I know you've mentioned this before and I've already refactored some of the code responsible for this.
I've already addressed this, and I've gone back and marked the change with this issue #:
* [D] [Issue #26046] To minimize RAM usage at the cost of cache resolution, decreased the number of blocks that the local cache will use (in memory) for drives < 8 TB.
This will reset cache usage data.
Here's the full chart of RAM usage by the local on-disk cache, with this change:
- Drives < 3 TB: Base cost is 25 MB and up to 131 MB will be used.
- Drives < 8 TB: Base cost is 50 MB and up to 262 MB will be used.
- Drives >= 8 TB: Base cost is 100 MB and up to 524 MB will be used.
This setup attempts to maintain at least 1 MB of cache resolution for drive sizes up to 1 PB. The base cost is always necessary, and the cache will use up additional RAM as the it fills up. Note that the maximum is only used when the local cache contains data equal to the total size of the disk (not the maximum cache size specified in the UI). So for example, if you have a 1 PB drive, and 1 PB of that data is stored locally, the local cache will use up 524 MB of RAM (this is the worst possible scenario, all other cases will use less memory).
Generally speaking, if your local cache is relatively small compared to the total size of the drive, then you will be using something close to the base cost.