Blocks Per Read
blocks per read blocks
Every time Zim Server has to read data from Zim files stored on disk, the read operations are performed in the number of blocks at a time (that is, blocks are read in a single operation) thus possibly reducing the number of physical accesses to disk and optimizing the overall performance of the system.
However, these read operations depend on a number of factors like speed of the disk drive, functionality of this disk drive, number of buffers that the operating system maintains in memory, type of operation being performed by the Zim application (that is, mainly a sequential or a random access), number of Zim users, etc.
Literally, Zim Server takes the number of blocks and incorporates these blocks into its buffers. The bigger the number of blocks, the bigger is the chance of subsequent Zim operations will find these buffers already in memory but at the expense of more CPU processing and possibly at the expense of removing some existing buffers. On the other hand, the smaller the number of blocks, the lower the chance of blocks can be found in memory but also the CPU activity is smaller.
In general, values between 1 and 8 are suggested.
Remark: This option has no effect from Zim 9.50 on and will be probably removed in the future.
Any directory path.