maximum locks locks The number of locks is the maximum number of locks that Zim Server can handle simultaneously. This means that the sum of all locks used in all ongoing transactions cannot exceed this number. Consequently, the larger the number of users, the bigger the number of locks needed, and, correspondingly, more shared memory…
Read more
maximum data blocks blocks This is the number of real blocks of data kept in memory at a given time by Zim Server to process transactions. The bigger the number, the faster transactions will be because more data will be available all the time. Its number depends only on the available shared memory. If users…
Read more
pending timeout cycles When an object requested by some operation being performed by Zim Server is not available (for instance, locks, blocks, etc.), the request goes to a list of pending objects and stays in the list until the object request can be satisfied. In this list, the object stays for the number of cycles…
Read more
checkpoint transactions nn This option indicates how many transactions must be committed to the temporay log file before performing a checkpoint that commits ongoing transactions to disk. The smaller the number of transactions, less efficient will be the overall performance of the system, but the databases involved will be more often updated. If the number…
Read more
scatter table links nn Number of links to blocks participating in transactions. This is the real size of the larger transaction possible in blocks for transactions that write blocks. For transactions that read blocks, these links can be reused within the same transaction. After finishing the transaction, either by a normal commit or by aborting…
Read more
pending sleep milliseconds When an object requested by some operation being performed by Zim Server is not available (for instance, locks, blocks, etc.), the request goes to a list of pending objects and stays in the list until the object request can be satisfied. In this list, the object availability is checked every number of…
Read more
checkpoint buffers buffers The option buffers indicates how many buffers must be written to the temporary log file before performing a checkpoint that commits ongoing transactions to disk. If this limit is reached while transactions are in process, the checkpoint will happen only after all transactions have finished to guarantee atomic transactions. The smaller the…
Read more
This option is not used by Zim Server and might be removed in future releases. datablock timeout milliseconds The time milliseconds indicates how long a buffer is going to stay in memory before Zim Server can use it to make additional room for new buffers being read. When a Zim session make a request to…
Read more
server port number port This configuration option establishes the port number used by Zim Server to talk to all the users that try to log on. Valid Settings A number from 1024 to 32765. Windows 6002 UNIX 6002
buffers per user buffers This option specifies the number of buffers to be allocated by each user to process data provided by Zim Server. The buffer allocation happens only in the client side and is independent of locks. Valid Settings Any directory path. Windows 1000 UNIX 1000
English 
Portuguese