did you read it the article? there's a large section on redis
the author says it's bad design, but has entirely missed WHY it wants overcommit
did you read it the article? there's a large section on redis
the author says it's bad design, but has entirely missed WHY it wants overcommit
You haven't made a connection, though. What does fork have to do with overcommit? You didn't connect the dots.
If you turn overcommit off then when you fork you double the memory usage. The pages are CoW but for accounting purposes it counts as double because writes could require allocating memory and that's not allowed to fail since it's not a malloc. So the kernel has to count it as reserved.