Speaking very generally, overall performance is usually best when the Cache Allocation Size is a value less than 40% of the physical memory on the system, and the Configuration setting Max cache engine Memory Usage is set to a value greater than 40%. Your exact optimal settings will depend on the size of your data files, the number of other applications running on the system, and the amount of memory installed in the computer.
The settings available under Cache Engine Debugging perform the same functions for the client cache as similar settings under
Server Debugging perform for the main database engine. For more information about each setting, see the related server setting:
This setting specifies whether the client cache should be used. If this setting is Off, then the client caches single records in a relatively small fixed-size cache on the client workstation. If this setting is
On, then the client uses the Cache Engine, if it is loaded in memory. If the Cache Engine is not loaded, this setting has no effect.
This setting controls runtime server support. If enabled with the value Yes, the current user name and password for the drive on which you are presently running are used. To enable RTSS with a different username, enter “
user_name,password.”
Note that you may use a fully qualified NDS user name in the format CN=user_name.O=
organization,
password. The user name may also be a simple Bindery name. The first entry in the Bindery context list must contain the simple name or the NDS login fails. If the NDS login fails for a simple name, a Bindery login is attempted. The Bindery login may cause delays while the login attempt is processing.