Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Duplicated memory and just overhead from running separate processes

fork(2) does COW. With careful design† forking a new process only results in new and modified pages being not shared.

† Hard! But single-process threads + security is hard too.

http://unix.stackexchange.com/questions/58145/how-does-copy-...



Only on Linux, POSIX does not mandate CoW and Windows does not have a similar API.


While not mandatory, I always sort of assumed BSD and Darwin do the same...

Just wanted to point out that memory usage isn't necessarily inherent to multiprocess, but with a sizable portion of users on Windows the point is practically moot anyway.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: