-cl server option

Sets a minimum cache size as a lower limit to automatic cache resizing.

Syntax
{ dbsrv11 | dbeng11 } -cl { size[ k | m | g | p ] } ...
Applies to

Windows, Unix, Mac OS X

Remarks

This option sets a lower limit to the cache. If you specify an initial cache size with the -c option, then the minimum cache size is the same as the initial cache size. If the initial cache size is not specified, then the default initial cache size is 2 MB on Windows and 8 MB on Unix.

The size is the amount of memory, in bytes. Use k, m, or g to specify units of kilobytes, megabytes, or gigabytes, respectively.

The unit p is a percentage either of the physical system memory, or of the maximum non-AWE cache size, whichever is lower. The maximum non-AWE cache size depends on the operating system. For example:

  • 2.8 GB for Windows 32-bit Advanced Server, Enterprise Server and Datacenter Server

  • 3.8 GB for the 32-bit database server running on Windows x64 Edition

  • 1.8 GB on all other 32-bit systems

  • On Windows Mobile, the p option specifies a percentage of available physical memory

If you use p, the argument is a percentage. You can use % as an alternative to P, but as most non-Unix operating systems use % as an environment variable escape character, you must escape the % character. To set the minimum cache size to 50 percent of the physical system memory, you would use the following:

dbeng11 -cl 50%% ...

This option is ignored if you are using an AWE cache. You can use the -cw option to create a larger cache using AWE. See -cw server option.

See also
Example

The following example starts a server named silver that has a minimum cache size of 5 MB and loads the database file example.db:

dbeng11 -cl 5m -n silver "c:\example.db"