eG Monitoring
 

Measures reported by LnDatabaseTest

This test reports database related metrics of the Lotus Domino server. The measures made by the test are as follows:
Measurement Description Measurement Unit Interpretation
Buffer_control_pool_size The size of the buffer control pool MB

 
Buffer_control_pool_used The number of bytes used in the buffer control pool MB

The value 0 may indicate that the measure's value is too large to be passed via snmp
Buffer_pool_allocated The number of bytes allocated from the buffer pool MB

 
Buffer_pool_max The maximum size of the buffer pool MB

 
Buffer_pool_used The number of buffers used from the buffer pool MB

 
NSF_pool_size The size of the NSF Pool KB

The NSF Buffer Pool is a section of memory dedicated to buffering I/O transfers between the NIF (Notes Index Facility) indexing functions and disk storage. By changing the size of NSF Buffer Pool you can control the size of the memory section used for this buffering. The NSF Buffer Pool is the only Domino memory pool that is configurable by the user. Therefore, while setting the NSF buffer pool size, you need to consider the number of users, the size and number of views, and the number of databases.
NSF_pool_used The amount of space used in the NSF pool KB

If the value of this measure decreases consistently, it indicates a steady erosion of space in the NSF pool. Resize the NSF pool, so that more memory is available for indexing or buffering I/O transfers.
Buffer_pool_percent_reads The percentage of buffer pool reads Percent

 

Buffer_pool_reads The number of buffer pool reads Number

 
Buffer_pool_writes The number of buffer pool writes Number

 
Current_cache_entries The number of databases currently in the cache Number

Administrators should monitor this number to see whether it approaches the NSF_DBCACHE_ MAXENTRIES setting. If it does, it indicates that the cache is under pressure. If this situation recurs, the administrator should increase the setting for NSF_DBCACHE_ MAXENTRIES.
Db_cache_hits The number of times an lnDBCacheInitialDbOpen is satisfied by finding a database in the cache Number

 
Db_cache_initial_opens The number of times a user/server opened a database that was not already being used by another user/server Number

By comparing this number to Db_cache_hits, administrators can gauge the effectiveness of the caching activity.
Db_cache_hit_ratio The percentage of hits to opens Percent

A high 'hits-to-opens' ratio indicates the database cache is working effectively, since most users are opening databases in the cache without having to wait for the usual time required by an initial (non-cache) open. If the ratio is low (in other words, more users are having to wait for databases not in the cache to open), the administrator can increase the NSF_DBCACHE _MAXENTRIES settings.
Db_cache_max_entries The number of databases that the server can currently hold in its cache Number

 
Db_cache_rejections The number of times a database is not placed into the cache Number

A database might not be placed into the cache when it is closed because lnDB Cache Current Entries equals or exceeds lnDBCacheMaxEntries * 1.5. This number should stay low. If it begins to rise, you should increase the NSF_DbCache_ Maxentries settings.