| | The ntdbsmgr.exe or PSQL Component processes are using too many resources |
| Description | The NTDBSMGR.exe process on the server is using excessive amounts of CPU and RAM. This is a process used by Pervasive/Actian/Zen. |
| Cause | The Pervasive Control Center doesn't have the correct settings for configuring the engine, or they need to be optimized. |
| Resolution | [BCB:5:Third-party support:ECB] - Have all users log out of Sage. Check the Pervasive Monitor/Zen Monitor to ensure that no data files are in use.
- Access the Control Center.
- Version 15.1 and older: on the file server, click Start, All Programs, Pervasive PSQL, 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 note)
NOTE: Cache Allocation Size in MB: Set to at least the size of the largest individual data file. Allow room for growth but don't go over 2048 or 2 GB. A good starting point is 64. - Number of Input/Output Threads = 64
- Max MicroKernel Memory Usage = (variable, see note)
NOTE: Max MicroKernal Memory Usage: Base this value on the total Random Access Memory (RAM) in the system and other functions that the server performs. If the server performs functions other than Sage, lower the percentage to leave resources for other applications. If it’s a dedicated Sage server, you can raise the percentage. Don't exceed 12 GB total allocation. - Click Apply and Yes to Restart the Engines.
|
|