Is it more simple to kill the preallocated process? For now, we don't use preallocated process for debug build, it is weird. We would like to fix it. That is why Ting is asking the reason that the preference is there. So, if any one know it, please leave a message.
Thank you! ----- Original Message ----- From: "Dave Hylands" <[email protected]> To: "Mike Lee" <[email protected]> Cc: "Kyle Huey" <[email protected]>, "Ting-Yu Chou" <[email protected]>, "fxOS Performance" <[email protected]>, [email protected], "Thinker Li" <[email protected]> Sent: Tuesday, August 12, 2014 1:09:30 PM Subject: Re: help needed: Any perf tests depend on preference "dom.ipc.processPrelaunch.eanbled"? I don't know if any perf tests rely on that setting or not. The only thing I can think of is that with som.ipc.processPrelaunch.enabled set to false, you would be able to determine your wost case startup time (since using the preallocated process isn't a guarantee, just an optimization that in optimal conditions allows us to perform some of the initializaton before the user launches an app. If the user launches 2 apps in close succession, then the second app will most likely be launched cold not use the preallocated app (if you don't consider Nuwa). Dave Hylands ----- Original Message ----- > From: "Mike Lee" <[email protected]> > To: "Kyle Huey" <[email protected]>, "Ting-Yu Chou" <[email protected]>, > "fxOS Performance" <[email protected]>, [email protected] > Cc: "Dave Hylands" <[email protected]>, "Thinker Li" <[email protected]> > Sent: Monday, August 11, 2014 10:01:50 PM > Subject: Re: help needed: Any perf tests depend on preference > "dom.ipc.processPrelaunch.eanbled"? > Hub, Eli, and Dave, > Can any of you answer Ting's question re: perf tests depending on the > dom.ipc.processPrelaunch.enabled preference? > Thanks, > Mike > Kyle Huey wrote: > > I don't think that's used for performance testing. If it is it would be > > pretty easy to work around by setting the process launch time to something > > quite high and then launching an app before the one you want to measure. > > > > - Kyle > > > > ----- Original Message ----->> From: "Ting-Yu Chou" <[email protected]> > >> To: "Mike Lee" <[email protected]> > >> Cc: "Kyle Huey" <[email protected]>, "Dave Hylands" > >> <[email protected]>, "Thinker Li" <[email protected]> > >> Sent: Monday, August 11, 2014 8:24:16 PM > >> Subject: help needed: Any perf tests depend on preference > >> "dom.ipc.processPrelaunch.eanbled"? > >> > >> Hi Mike, > >> > >> I asked follwing on IRC #fxos-perf, but it was late night in US, so I send > >> you > >> this email in case you have better idea whom should I ask. > >> > >> <ting> hi, I am not sure whom to ask, but do we have any performance > >> (launch > >> time) tests depend on preference "dom.ipc.processPrelaunch.enabled"? > >> <ting> I am asking because Nuwa is default disabled by the preference on > >> debug > >> builds, and in bug 1050122 we are thinking to change it to default > >> enabled, but Thinker remembers some startup time tests depend on it. > >> > >> I have grep, and there are only > >> > >> ./gecko/modules/libpref/test/unit_ipc/test_user_default_prefs.js > >> ./gecko/dom/ipc/tests/test_NuwaProcessCreation.html > >> ./gecko/dom/ipc/tests/test_NuwaProcessDeadlock.html > >> ./gecko/dom/browser-element/mochitest/priority/test_Preallocated.html > >> > >> using it. > >> > >> Thank you, > >> Ting _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
