6 ms·

It can come up in use-cases with very large in-memory databases, caches or indexes that would otherwise have to be rebuilt/reloaded on reboot, taking hours. Ima

It can come up in use-cases with very large in-memory databases, caches or indexes that would otherwise have to be rebuilt/reloaded on reboot, taking hours. Imagine having, say 4TB of index in memory and needing to patch that server. With persistent memory you could be back up and running much more quickly. Especially helpful when you have many of these types of servers that have to all get patched in some sequence. This is not a home-use-case, but it certainly exists today in larger Enterprises. So it's not (necessarily) about having a very fast filesystem, it's about having persistent memory.

tentacleuno 5y ago
> This is not a home-use-case, but it certainly exists today in larger Enterprises. Part of me hopes someone in here proves you wrong :-) Us techies do mad things sometimes...
Dylan16807 5y ago
What kind of patching? Is the goal to say "okay, here is a persistent chunk of memory with a file or program in it, keep it preserved while the OS reboots, then if it's a program reconnect the files and sockets it was using"? Because you can just remove the word 'persistent' and do that today. Most hardware shouldn't wipe memory on a reboot, and if it does talk to your vendor for a BIOS option. And all the support code you need in your OS should be roughly the same.