Multi-process Firefox brings 400-700% improvement in responsiveness

Re:Multi-process Firefox brings 400-700% improvement in resp... by lloeki on Wednesday September 07, 2016 @03:16AM (#12441414)

> 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-...

[ Parent | on HN ]

Re:Multi-process Firefox brings 400-700% improvement in resp... by AstralStorm on Wednesday September 07, 2016 @03:55AM (#12441530)

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

[ Parent | on HN ]

Re:Multi-process Firefox brings 400-700% improvement in resp... by lloeki on Wednesday September 07, 2016 @07:06AM (#12442269)

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.

[ Parent | on HN ]