Journal File Synchronization

 

Under normal operating conditions, when a transaction is committed, DBMaker initiates a two-step process with regards to the journal blocks involved in the transaction. The first step is to flush the relevant journal blocks into the file system of the operating system, or the operating system's cache. The second step is to force the operating system to write these journal blocks to disk, so that the transaction is preserved in the event of a system crash. It is possible to greatly increase the performance of the commit transaction process if the second step of this process is omitted. The journal blocks in this case remain in the operating system's cache until the operating system writes them to disk. However, if the system crashes at this point, the records of any transactions that were still in the operating system's cache will be lost.


Related topic:

Changing System Control Settings