Help Center/ GeminiDB/ GeminiDB Redis API/ FAQs/ Database Usage/ How Is the Number of Keys Collected? Why Is the Number of Keys Monitored by GeminiDB Inaccurately Increasing After Migration?
Updated on 2025-07-29 GMT+08:00
View PDF
Share

How Is the Number of Keys Collected? Why Is the Number of Keys Monitored by GeminiDB Inaccurately Increasing After Migration?

  • The number of keys is not updated in real time. Instead, it is calculated by asynchronously scanning multiple nodes and aggregating their data. If the growth rate of keys exceeds the scan rate, for example, when data is migrated or when a large volume of data is injected quickly, the statistics collection will be delayed. The key scan speed is determined by the key-scan-batch parameter. Since this speed is constant, the growth of the key quantity maintains steady.
  • To speed up the scan, go to the instance details page, choose Parameters in the navigation pane, search for key-scan-batch, and increase the value. For details, see Modifying Parameters of an Instance. Setting key-scan-batch to a larger value will consume more CPUs. During migration, you can increase the value. After the migration is complete, you are advised to use the default value to prevent excessive CPU consumption.
Figure 1 Modifying key-scan-batch
Parent Topic: Database Usage