Hotspot Key Statistics
In the distributed architecture, if applications access a node in a short period of time, the resource usage of the node is too high, affecting the normal running of the database. GaussDB provides the function of quickly detecting hotspot keys to quickly determine whether there are hotspot keys and the distribution of hotspot keys.
enable_hotkeys_collection
Parameter description: Specifies whether to automatically collect statistics on the accessed key values in the database.
If you set parameters using gs_guc set, you need to restart the database for the GUC parameters to take effect. During the restart, hotspot key information is cleared.
When the GUC parameter is disabled, the query result of the hotspot key is empty and a message is displayed indicating that the GUC parameter is disabled. However, when the function is disabled, the hotspot key clearance API can still be used.
Parameter type: Boolean
Unit: none
Value range:
- on indicates that the statistics collection function is enabled.
- off indicates that the auditing function is disabled.
Default value: off
Setting method: This is a SUSET parameter. Set it based on instructions provided in Table 1.
Setting suggestion: Enable this parameter when the hotspot detection function is required. After this parameter is enabled, the TPC-C performance deteriorates by less than 5%, and each instance occupies 500 MB memory resources.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
