On Tue, Jun 9, 2009 at 3:59 AM, Dean McNamee<[email protected]> wrote: > On Tue, Jun 9, 2009 at 10:57 AM, Lei Zhang<[email protected]> wrote: >> Does this mean the zygote manager process is the parent process for >> the browser process and all renderer processes? Whereas before the >> browser process was the parent to all renderer processes. > > Yeah, I just took a poke at this, it seems that > > zygote > \ browser > \ renderer > \ renderer ...
Yes. I tried leaving the initial process as browser, and making the zygote its first child, but it was hard to get all the UI tests passing that way (the process filtering in chrome_process_utils.cc in particular didn't work that way). > Is there a design document or anything somewhere? No, but I can write one this morning. > Also, did we get an measurements on tab startup performance, memory > sharing, etc? My measurements on tab startup showed no clear effect. But http://build.chromium.org/buildbot/perf/linux-release/startup/report.html?history=150 shows that the 'startup' measurement increased by about 5ms and got quite a bit more variable. (My measurements were all with the old parentage arrangement, with the zygote as the first child, perhaps that change made a difference.) - Dan --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
