Update valkey.conf

Co-authored-by: Ping Xie <[email protected]>
Signed-off-by: zhaozhao.zz <[email protected]>

valkey.conf

@@ -1998,37 +1998,38 @@ aof-timestamp-enabled no
 #    entries for a specific log type and reclaim memory, use the `COMMANDLOG RESET` 
 #    subcommand followed by the log type.
 #
-# You can configure the slow threshold with two parameters: one tells the server
-# what is the execution time, in microseconds, to exceed in order for the
-# command to get logged, and the other parameter is the length of the
-# slow log. When a new command is logged the oldest one is removed from the
-# queue of logged commands.
-#
-# The following time is expressed in microseconds, so 1000000 is equivalent
-# to one second. Note that a negative number disables the slow log, while
-# a value of zero forces the logging of every command.
+# SLOW Command Logs
+# The SLOW log records commands that exceed a specified execution time. The execution time 
+# does not include I/O operations, such as client communication or sending responses. 
+# It only measures the time spent executing the command, during which the thread is blocked 
+# and cannot handle other requests.
+#
+# The threshold is measured in microseconds.
+#
+# Backward Compatibility: The parameter `slowlog-log-slower-than` is still supported but 
+# deprecated in favor of `commandlog-slow-execution`.
 commandlog-execution-slower-than 10000
 # There is no limit to this length. Just be aware that it will consume memory.
 # You can reclaim memory used by the slow log with SLOWLOG RESET or COMMANDLOG RESET SLOW.
 commandlog-slow-execution-max-len 128
-
+#
 # LARGE_REQUEST Command Logs
 # The LARGE_REQUEST log tracks commands with requests exceeding a specified size. The request size 
 # includes the command itself and all its arguments. For example, in `SET KEY VALUE`, the size is 
 # determined by the combined size of the key and value. Commands that consume excessive network 
 # bandwidth or query buffer space are recorded here.
-
+#
 # The threshold is measured in bytes.
 commandlog-request-larger-than 1048576
 # Record the number of commands.
 commandlog-large-request-max-len 128
-
+#
 # LARGE_REPLY Command Logs
 # The LARGE_REPLY log records commands that produce replies exceeding a specified size. These replies 
 # may consume significant network bandwidth or client output buffer space. Examples include commands 
 # like `KEYS` or `HGETALL` that return large datasets. Even a `GET` command may qualify if the value 
 # is substantial.
-
+#
 # The threshold is measured in bytes. 
 commandlog-reply-larger-than 1048576
 commandlog-large-reply-max-len 128