| The ntdbsmgr.exe or PSQL Component processes are using too many resources. |
Cause | The settings in the Pervasive Control Center for configuring the engine are improperly set or need to be optimized. |
Resolution | [BCB:5:Third-party support:ECB]
- All users must be logged out of Sage. Check the Pervasive Monitor/Zen Monitor to ensure that no data files are in use. See How do I use the Pervasive Software Monitor Utility (PMU/PSMU) to unlock a file on a server that uses a Windows operating system?
- Access the Control Center:
- Version 15.1 and older: on the file server, click Start, All Programs, Pervasive PSQL, PSQL Control Center (or search PSQL Control Center)
- Version 16.1 to 24.1: Start, All Programs, Actian PSQL 12, PSQL Control Center & Documentation
- Version 24.2 and later: Start, All Programs, Actian Zen 15, Zen Control Center & Documentation
- Click Configure Local Engine
- In the Performance tuning section, adjust the settings:
- Communication Threads = 32
- Cache Allocation Size in MB = (variable, see notes below)
- Number of Input/Output Threads = 64
- Max MicroKernel Memory Usage = (variable, see notes below)
- Click Apply and Yes to Restart the Engines.
Notes: Cache Allocation Size in MB: Should be set to at least the size of the largest individual data file, and allow room for growth (but not go over 2048 or 2 GB). A good starting point might be 64. Max MicroKernal Memory Usage: This value should be based on the total Random Access Memory (RAM) in the system and other functions that the server performs. If the server is performing functions other than Sage, the percentage should be lower in order to leave enough resources for other applications. If it is a dedicated Sage server, then the percentage can be higher, although it should not exceed 12 GB total allocation in most cases. |
|