I think this may've gotten an order of magnitude better (not sure if that's due to changes on the TreeHerder side vs. on the Firefox side... probably some of it is due to me having a faster machine, too). If I follow bz's instructions from bug 1159470 comment 0, I now see these results in Firefox Nightly: ``` Style: 283 Layout: 233 ``` which are ~1/5 the values from comment 0. Here's a profile from the run where I captured those ^ values: https://share.firefox.dev/3cR55Ek Performing the same experiment in Chrome, I see results that are ~2x as slow: ``` Style: 447 Layout: 494 ``` So it seems we're doing better than the competition, and quite a bit better than we were doing when this was filed, so it's unclear that there's any clear improvements that could/should be made here. I think we can call this WORKSFORME.
Bug 1159819 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think this may've gotten an order of magnitude better (not sure if that's due to changes on the TreeHerder side vs. on the Firefox side... probably some of it is due to me having a faster machine, too). If I follow bz's instructions from bug 1159470 comment 0, I now see these results in Firefox Nightly: ``` Style: 283 Layout: 233 ``` which are ~1/5 the values from comment 0. Here's a profile from the run where I captured those ^ values: https://share.firefox.dev/3cR55Ek Performing the same experiment in Chrome 83, I see results that are ~2x as slow: ``` Style: 447 Layout: 494 ``` So it seems we're doing better than the competition, and quite a bit better than we were doing when this was filed, so it's unclear that there's any clear improvements that could/should be made here. I think we can call this WORKSFORME.