On 04/23/2015 07:43 AM, Ed Morley wrote:
Scrolling fluidity/general app responsiveness of Treeherder is massively
worse in Nightly compared to Chrome. eg try this in both:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central
The problem is even more noticeable when the "get next 50" buttons is
pressed at the bottom of the page.
I know last year a few people did some profiling (see deps of bug 1112352)
- however only two of the bugs are still open and the situation vs Chrome
is still pretty bad (if not more extreme now than it was previously).
Could someone who's a platform-profiling ninja do a massive favour and see
if there are any more platform bugs we can find for this? It seems like we
could use Treeherder as a useful real-world testcase for improving complex
webapp performance compared to Chrome - in addition to making devs lives a
little less janky whilst using Treeherder themselves.
If anyone does find anything, please add as deps of:
https://bugzilla.mozilla.org/show_bug.cgi?id=1112352
Many thanks :-)
Ed
Seems to be mostly JS and Reflow (I did some page load profiling, not the 'click
"get next 50"' case).
JS seems to execute some JIT'ed stuff, then JS::DoCallFallback, Invoke,
fun_apply, RunScript, Interpret, EnterBaseline...
Looks a bit suspicious, at least to my non-jit-profiling-educated eyes that we
fall out from the jit code.
Reflow seems to be mostly inline frame reflowing (even in the cases we reflow
tables).
I don't think these issues are quite the same as any of the bugs
https://bugzilla.mozilla.org/show_bug.cgi?id=1112352 depend on.
jandem, dbaron, could you profile this a bit to see if there is anything
obvious?
-Olli
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
