The database server
22
♦
Windows NT, Windows 95/98, NetWare 2 Mb
♦
UNIX 8 Mb
2 It computes a runtime-specific minimum default cache size, which is the
lesser of the following items:
♦ 25% of the machine’s physical memory
♦ The sum of the sizes of the main database files specified on the
command line. Additional dbspaces apart from the main database
files are not included in the calculation. If no files are specified, this
value is zero.
3 It allocates the greater of the two values computed.
NetWare database server
There is a trade off between memory for the database server and memory
for the NetWare file system buffers. A larger database server cache will
improve database server performance at the expense of NetWare file
system performance. If the database server cache is too big, NetWare will
report an error that there is insufficient memory for cache buffers.
NetWare memory requirements increase with every new directory and file
on the file server. To track memory usage on the NetWare server, load
monitor.nlm
(if it is not already loaded) and select "Resource Utilization".
Extra memory for your NetWare server computer could improve database
performance and/or file server performance dramatically.
"–ch command-line option" on page 23
–ca command-line option
When used as -ca 0, enforces a static cache size. The zero argument is
required.
[ dbsrv7 | dbeng7 ] -ca 0 ...
Windows NT, Windows 95/98, UNIX
Without setting
-ca to 0, the database server automatically takes additional
cache as needed. You can disable automatic cache increase due to high
server load by using -ca 0 on the command line. The cache size still increases
if the database server would otherwise run into the error
Fatal Error: dynamic
memory exhausted, or if the Java VM requires memory that would lead to a
fatal error.
This command-line option should be used only in the form
-ca 0. If -ca is
omitted, automatic cache growth is enabled.
See also
Function
Syntax
Applies to
Description
To Next Page
Loading...