Global SysCache Parameters
enable_global_syscache
Parameter description: Specifies whether to enable the global system cache function. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1.
Value range: Boolean
- on indicates that the global system cache function is enabled.
- off indicates that the global system cache function is disabled.
Default value: on
You are advised to use this parameter together with the thread pool parameter. After this parameter is enabled, you are advised to set wal_level of the standby node to hot_standby or higher if you need to access the standby node.
global_syscache_threshold
Parameter description: Specifies the maximum memory usage of the global system cache.
This is a SIGHUP parameter. Set it based on instructions provided in Table 1.
The enable_global_syscache parameter must be enabled.
Value range: an integer ranging from 16384 to 1073741824. The unit is KB.
Default value:
163840 (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, 60-core CPU/480 GB memory, 32-core CPU/256 GB memory, 16-core CPU/128 GB memory, 8-core CPU/64 GB memory, 4-core CPU/32 GB memory); 65536 (4-core CPU/16 GB memory)
Recommended calculation formula: MIN(Number of hot databases,Number of threads) x Memory size allocated to each database.
That is, global_syscache_threshold = min(count(hot dbs), count(threads)) x memofdb.
The number of hot databases refers to the number of frequently accessed databases. In thread pool mode, the number of threads is the sum of the number of threads in the thread pool and the number of background threads. In non-thread pool mode, the number of hot databases is used.
memofdb indicates the average memory allocated to each database. The background noise memory of each database is 2 MB. Each time a table or index is added, 11 KB memory is added.
If this parameter is set to a small value, memory is frequently evicted, and a large number of memory fragments cannot be recycled. As a result, memory control fails.
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