Although we have moved preloading into Nuwa, it still takes about 100ms for preallocated process to be ready. As Ting pointed out in bug 110624, if preallocated process can be ready within 20ms, we can fork right after user attempt to open an app and can load app URI directly after new process ready without having to wait for one more IPC message (LoadURI). Event if we can't make it ready in 20ms, making preallocated process ready faster can still shorten the interval that Nuwa need to wait before it can perform next fork. And having less operation roughly means that less copy-on-write page it touches, and make it smaller in memory when it is waiting.

We did have some sort of 3 or 5 second delay. Did we get rid of that yet?

(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) (Away 12/20-12/28) from comment #1) > We did have some sort of 3 or 5 second delay. Did we get rid of that yet? I don't think so.

(In reply to Patrick Wang (Chih-Kai Wang) (:kk1fff) from comment #0) > And having less operation roughly means that less > copy-on-write page it touches, and make it smaller in memory when it is > waiting. It might be worth adding the MemShrink tag to the whiteboard along with a comment with an estimation of how much memory this might save.