Parameters

<p>This article describes the parameters that you can modify in the Redis console.</p> <p><strong><span style="font-size:18px">Overview</span></strong></p> <p>This feature allows you to configure advanced parameters of the Redis engine to optimize the Redis performance.</p> <p><strong><span style="font-size:18px">Parameter Description&nbsp;</span></strong></p> <table border="1" cellpadding="0" cellspacing="0"> <tbody> <tr> <td style="background-color:#ededed; vertical-align:top; width:66px"> <p><strong>Parameter</strong></p> </td> <td style="background-color:#ededed; vertical-align:top; width:402px"> <p><strong>Description</strong></p> </td> <td style="background-color:#ededed; vertical-align:top"> <p><strong>Default</strong></p> </td> <td style="background-color:#ededed; vertical-align:top"> <p><strong>Value range</strong></p> </td> <td style="background-color:#ededed; vertical-align:top"> <p><strong>Cluster instance</strong></p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>hash-max-ziplist-entries</p> </td> <td style="vertical-align:top; width:402px"> <p>Use the ziplist encoding format when the number of all key-value pairs in the hash table of the hash object is less than or equal to the specified value.</p> </td> <td style="vertical-align:top"> <p>512</p> </td> <td style="vertical-align:top"> <p>0 to 1024</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>hash-max-ziplist-value</p> </td> <td style="vertical-align:top; width:402px"> <p>Use the ziplist encoding format when the maximum length of each key or value in the hash table of the hash object is less than or equal to the specified bytes.</p> </td> <td style="vertical-align:top"> <p>64</p> </td> <td style="vertical-align:top"> <p>0 to 1024</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>list-compress-depth</p> </td> <td style="vertical-align:top; width:402px"> <p>Number of nodes at both ends of the list that are not compressed:</p> <p><strong>0</strong>&mdash;No compression.</p> <p><strong>1</strong>&mdash;Each node at both ends is not compressed, and the intermediate nodes are compressed.</p> <p>&hellip;</p> <p><strong>n</strong>&mdash;<em>N</em> nodes at both ends are not compressed, and the intermediate nodes are compressed.</p> </td> <td style="vertical-align:top"> <p>0</p> </td> <td style="vertical-align:top"> <p>0 to 512</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>set-max-intset-entries</p> </td> <td style="vertical-align:top; width:402px"> <p>Use the intset encoding format when the data in the Set has both of the following characteristics:</p> <ul> <li>String data type;</li> <li>64-bit signed integers with a cardinality of 10.</li> </ul> </td> <td style="vertical-align:top"> <p>512</p> </td> <td style="vertical-align:top"> <p>0 to 1024</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>zset-max-ziplist-value</p> </td> <td style="vertical-align:top; width:402px"> <p>Use the ziplist encoding format when the maximum length of each key or value in the Sorted set is less than or equal to the specified value.</p> </td> <td style="vertical-align:top"> <p>64</p> </td> <td style="vertical-align:top"> <p>0 to 1024</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>zset-max-ziplist-entries</p> </td> <td style="vertical-align:top; width:402px"> <p>Use the ziplist encoding format when the number of all key-value pairs recorded by the Sorted set is less than the specified number.</p> </td> <td style="vertical-align:top"> <p>128</p> </td> <td style="vertical-align:top"> <p>0 to 1024</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> <tr> <td style="vertical-align:top; width:66px"> <p>notify-keyspace-events</p> </td> <td style="vertical-align:top; width:402px"> <p>Keyspace notifications. This parameter allows the client to receive Redis dataset modification events through the Redis publish-subscribe feature.</p> <ul> <li><strong>K</strong>&mdash;Keyspace notifications. All notifications are prefixed with __keyspace@&lt;db&gt;__.</li> <li><strong>E</strong>&mdash;Keyevent notifications. All notifications are prefixed with __keyevent@&lt;db&gt;__ as the prefix.</li> <li><strong>g</strong>&mdash;Notifications about general type-irrelevant commands, such as DEL, EXPIRE, and RENAME.</li> <li><strong>$</strong>&mdash;Notifications about string commands.</li> <li><strong>l</strong>&mdash;Notifications about list commands.</li> <li><strong>s</strong>&mdash;Notifications about set commands.</li> <li><strong>h</strong>&mdash;Notifications about hash commands.</li> <li><strong>z</strong>&mdash;Notifications about sorted set commands.</li> <li><strong>x</strong>&mdash;Overdue events. An overdue event is sent whenever an expiring key is deleted.</li> <li><strong>e</strong>&mdash;Eviction events. An eviction event is sent whenever a key is deleted based on the maxmemory policy.</li> <li><strong>A</strong>&mdash;Alias for all g$lshzxe parameters.</li> </ul> </td> <td style="vertical-align:top"> <p>N/A</p> </td> <td style="vertical-align:top"> <p>N/A</p> </td> <td style="vertical-align:top"> <p>Supported</p> </td> </tr> </tbody> </table>
Did the above content solve your problem? Yes No
Please complete information!

Call us

400-151-8800

Email us

cloud@pingan.com

Online customer service

Instant reply

Technical Support

cloud products