Parameter:
NSF_LogCloseShort description: Logs when NSF databases are removed from the database cache and closed – helpful for cache tuning (
MaxEntries / MinEntries).Profile
Parameter | NSF_LogClose |
Category | Logging / Debug |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = off, 1 = one line per close, 2 = incl. reason (TTL, pressure, idle) |
Description
When the database cache constantly closes NSFs and reopens them shortly afterward, performance suffers – but the root cause is hard to see without logging.
NSF_LogClose=1 writes a line for every NSF close to the console log; NSF_LogClose=2 additionally includes the reason (cache full, TTL expired, idle timeout). This makes it possible to decide deliberately whether NSF_DbCache_Maxentries, NSF_DbCache_MinEntries, or idle timeouts need adjusting.Example configuration
NSF_LogClose=2
Notes & pitfalls
- Quickly generates a large number of log entries – enable only temporarily for tuning sessions.
- Takes effect after a server restart.
- Ideally combine the analysis with the
show stat Database.DbCache*statistics.
- For ongoing logging in production, consider using only level
1and filtering to critical NSFs.