This makes no sense to me. This push seems to have unregressed the regression from my previous push. First I though I had pushed wrong patches from my MQ, but I checked the changesets and none touched nsScriptLoader.
What's going on here?
sicking, should the plan to back out the nsScriptLoader patch be canceled now that Dromaeo is magically unregressing itself?
On Mon, Sep 20, 2010 at 12:05 PM, Henri Sivonen <hsivo...@iki.fi> wrote: > sicking, should the plan to back out the nsScriptLoader patch be canceled now that Dromaeo is magically unregressing itself?
Is this a PGO-related artifact? Would be good to retest those builds a couple of times and see what we get. PGO can be deep magick, not always friendly.
Chatted a bit here and given that this has been in for a few days while still not being able to figure out exactly what's going on, lets back it out and see if we gain back the perf, and based on that figure out where to go next.
If the recent un-regressions really did give back the loss, then backing out shouldn't affect perf and we can land again. At that point PGO seems like a good direction to point blame. Hopefully that can happen quickly enough that we can still have this in for beta7. If backing out does give us back the perf, then we need to try to reproduce locally and try to pin-point the issue.
On Mon, Sep 20, 2010 at 12:13 PM, Mike Shaver <mike.sha...@gmail.com> wrote: > On Mon, Sep 20, 2010 at 12:05 PM, Henri Sivonen <hsivo...@iki.fi> wrote: >> sicking, should the plan to back out the nsScriptLoader patch be canceled now that Dromaeo is magically unregressing itself?
> Is this a PGO-related artifact? Would be good to retest those builds > a couple of times and see what we get. PGO can be deep magick, not > always friendly.
> Chatted a bit here and given that this has been in for a few days > while still not being able to figure out exactly what's going on, lets > back it out and see if we gain back the perf, and based on that figure > out where to go next.