The Sybase workgroup databases make use of a reserved cache memory. The optimum setting will depend upon the size of the database, number of users and total available RAM.
| Total Workstation RAM | Recommended Sybase Reserved Cache |
|---|---|
General recommended values are shown in the table left.
If the reserved database cache is set to too high a value, other server processes or any Podium client on the same computer are adversely affected. If the reserved database cache value is set too low, the application performance will be reduced as it waits for the database server.
The Sybase reserved cache memory is not available to other applications when the database engine is running.
There is no point reserving more memory for the database than the overall Podium database size including the files podium2.db, bom.db, podaudit.db, podium2.log and any temporary files created by the database (For Netware and Linux platforms, these are in the database directory; for Windows they are in the System 32 directory).
For standalone single user databases, the reserved database cache can be modified by reinstalling Podium (skipping overwrite of the existing database).
For further information on changing the reserved cache and other aspects of configuration on multi-user databases, consult the Sybase documentation.
Memory available to and reserved for the database engine is a major determinant of Podium performance.