Why does L2 deferred write eat physical memory?
Posted: Wed Dec 12, 2018 2:14 pm
I recently built a desktop computer, and wanted to revisit Primocache as a 'landing zone' for a slew of external 8tb SMR hard drives.
I'm not interested in caching, or L1 memory at all, I just want to use a 500GB SSD RAID-0 as a write-buffer for my slow disks.
Like the title says, I don't understand why (when not wanting read-buffer at all) primocache still requires GB's of physical memory to achieve a reasonably small block size?
I understand using physical memory as a sort of 'index' of the cache contents, but I do not want read-cache at all. Only write.
I'm not interested in caching, or L1 memory at all, I just want to use a 500GB SSD RAID-0 as a write-buffer for my slow disks.
Like the title says, I don't understand why (when not wanting read-buffer at all) primocache still requires GB's of physical memory to achieve a reasonably small block size?
I understand using physical memory as a sort of 'index' of the cache contents, but I do not want read-cache at all. Only write.