Kbase P131946: Is more memory needed when -tablerangesize is increased?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/04/2010 |
|
Status: Verified
GOAL:
Is more memory needed when -tablerangesize is increased?
GOAL:
How much memory does -indexrangesize need?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
Progress 9.x
Progress 8.x
FIX:
The range of tables and indices monitored is defined by the server startup parameters:
Tables: -basetable n -tablerangesize n
Indices: -baseindex n -indexrangesize n
The basetable and baseindex can be changed at run-time by updating the _StatBase VST.
The range cannot be changed because the backing shared memory needs to be pre-allocated.
The shared memory cost is : 32 bytes per table per user + 40 bytes per index per user based on the size of the table and index ranges specified at startup.
Example: 100 users monitoring 100 tables and 100 indexes:
100 (users) * 100 (tables) * 32 (bytes per table) + 100 (users) * 100 (indexes) * 40 (bytes per index) = 720,000 bytes (about 0.5 MB of shared memory)