redis uses the copy-on-write property of fork() to implement saving
which is elegant and completely legitimate
How does fork() work with vm.overcommit=2?
A forked process would assume memory is already allocated, but I guess it would fail when writing to it as if vm.overcommit is set to 0 or 1.
Can you elaborate on how this comment is connected to the article?
How does fork() work with vm.overcommit=2?
A forked process would assume memory is already allocated, but I guess it would fail when writing to it as if vm.overcommit is set to 0 or 1.