Maximum Cache Size
Synopsis
egr.eai.fscache.size=<size-in-KiB>
Default Value: unlimited
This option sets the target cache size. The actual amount of disk space used may be larger because:
-
The cache cleaner does not delete objects that are in use. Therefore, if the target size of the cache is quite small, the total size of all used objects may be greater than the target size.
-
The cache performs its size computations in KiB (number of bytes divided by 1024 and rounded up to the next integral value). If the block size of the file system is greater than one KiB, files may actually use more disk space than assumed by the cache.
-
The size of file system meta data (i-nodes, directories) is not considered by the cache at all.
The default value unlimited is used if the option is not specified, or if the option value is an empty string. It must not be specified literally as the option value.
If the cache size is not limited, the Online Configurator does not remove unused images as the cache fills up. If disc space is not an issue, the cache size may be left unlimited without significant impact on the cache’s performance1.
Footnotes
-
Assuming a cache size of one terabyte, and an average file size of 50 kilobyte, the leaf directories storing the cached files contain, on average, somewhat more than 300 files. Even for file systems with linear directory search this is still a reasonable size. File systems that use tree structures for their directories (XFS, EXT3, EXT4, among others) should be able to accommodate much larger caches. ↩