Help Center/ GaussDB/ Developer Guide(Distributed_V2.0-8.x)/ Configuring GUC Parameters/ GUC Parameters/ Statistics During the Database Running/ Hotspot Key Statistics
Updated on 2025-05-29 GMT+08:00
View PDF
Share

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: The statistics collection function is enabled.
  • off: The statistics collection 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.

Risks and impacts of improper settings: If this function is enabled, the TPC-C performance slightly deteriorates by less than 5%, and each instance occupies 500 MB memory resources.