3 ms·
How hard are you thinking? I can think of numerous scenarios where an entire working set being in RAM is useful and occasionally essential, and it is quite comm
by jsmthrowaway 10y ago
How hard are you thinking? I can think of numerous scenarios where an entire working set being in RAM is useful and occasionally essential, and it is quite common as an optimization in several industries. Finance comes to mind (kdb+ is designed to weaponize tons of RAM), as does high-scale Web operations. This is part of why solid state NVMe devices are compelling, too, to help bridge the gap, but it sounds like not for your purposes.
Even on the less complicated end, some years ago throwing a shitload of page cache at MongoDB was the only way to maintain high write loads, and eventually one reached a point where one had to keep an entire shard in cache. That bottom end threshold is lower than you think. I don't know if that's changed.
- warent 10y agoI could be wrong but it really sounds like you're talking about production. If that's the case then yes, I can respect the RAM requirement and it's almost too obvious to state that it isn't purposeless. The key here is it's a personal development workstation on which he has these resources. If that's a requirement, I would argue there's something fundamentally wrong with his development processes requiring that much data locally without even a server.