3 ms·
> That's a 1990s design assumption when memory was expensive Memory is still expensive: * Spreading things out in memory more causes more cache misses, which
by munificent 10y ago
> That's a 1990s design assumption when memory was expensive
Memory is still expensive:
* Spreading things out in memory more causes more cache misses, which lowers performance.
* Using more memory increases page faults, which lowers performance.
* I believe using more memory drains batteries faster on mobile devices, but I'm not sure exactly why. Maybe the effort spent shuttling stuff from virtual memory into real memory on page faults?
* On embedded devices, using more memory means you need to have more RAM, which increases the per-device manufacturing cost.
* Using more memory to represent code increases memory pressure, which leads to more GC cycles.
- sitkack 10y agoMobile probably turns off DRAM refresh for memory not allocated. RAM at rest still takes work to refresh.
- utorrent_dev 10y agoI agree. If you want things to be fast on a current Intel machine, keeping the code and data in cache means you can do ten times as much work before you have to do the next memory access. There's also the issue of additional latency from tertiary caches, like the disk, when you are under memory pressure.