Parameter:
NSF_DbCache_MaxentriesShort description: Maximum number of databases kept open simultaneously in the NSF database cache.
Profile
Parameter | NSF_DbCache_Maxentries |
Category | Performance / Memory |
Component | Server, Client |
Available since | R5 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Integer, calculated dynamically; typically 200–800 |
Description
The Domino database cache keeps opened NSF structures in memory so that repeated accesses can occur without reopening, reinitializing indexes, and reading header data. More cache entries mean higher hit rates and therefore significantly better I/O performance – at the cost of a bit more RAM.
NSF_DbCache_Maxentries sets the upper bound. Domino chooses the default automatically to match the hardware; on servers with many active databases and ample RAM, a manual increase is often worthwhile.Example configuration
NSF_DbCache_Maxentries=500
Notes & pitfalls
- Without an explicit setting, Domino picks automatically (typically 200–400) – usually fine.
- Values > ~1500 rarely provide measurable benefit and can become RAM-tight.
- Check the cache hit rate via
show stat database.dbcache.*, especiallyHits/Lookups.
- Increase on frequent
DBCache fullmessages.
- Works together with
NSF_Buffer_Pool_Size_MB– balance the two tuning values.
- The change only takes effect after a server / client restart.