Pervasive SQL 10.x ntdbsmgr process using 494Mb system memory

The database takes the memory in order to provide a data cache, which reduces disk I/O, and thus improves database performance.   Before reducing the PSQL cache size, you should look at your database size and decide if this makes sense.  If the sum of the sizes of all of your Btrieve files are only 200MB, then obviously you can shrink the L1 cache size (Cache Allocation) to 200MB and disable L2 cache (Max Microkernel Memory Size).  If your files total 4GB, though, then decreasing the cache will likely impact performance of the database.  

Honestly, with 3GB of RAM, using 0.5GB for the database seems pretty reasonable.  Feel free to set it as low as you want, though.

Can you describe how:
- i can find en check the db size
- i can set the cache size

thanks,
Pieter

>>- i can find en check the db size
Look for your database files.  These are defined by the application developer, and could have ANY extension, though they usually have an extension of BTR, MKD, DAT, FIL, or the like.  When in doubt, run the Pervasive Monitor program while users are in the application and look at the Microkernel/Active Files screen. Then, look at these files in the OS and sum up their sizes.

>>- i can set the cache size
Start/Run/PCC.  On the Welcome Screen, click on the link for Configure Local Engine.  Go to the Performance Tab.  The aforementioned settings will be there.  After changing them, restart the engine (or just reboot, if that's easier).  See the Help/Documentation screen in the PCC for more complete details on each of the settings.

I found some *.BTR files with the monitor application. Those are located in the folder that the clients use and take up about 5 Gb.

In attach the detail settings of the performance and memoery usage tabs.


perf1.jpg
perf2.png

You can certainly decrease memory usage, at the possible expense of performance. Its your call.