Re: Treeherder UI performance much worse in Nightly vs Chrome

2015-04-26 Thread smaug

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


Re: Treeherder UI performance much worse in Nightly vs Chrome

2015-04-23 Thread jmathies
Maybe this bug 1157409 bleeding through to non-apzc? Perf on tree herder sucks 
for me too, and I have apzc off today.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Treeherder UI performance much worse in Nightly vs Chrome

2015-04-23 Thread Aaron Klotz
I just tried it (I'm still running yesterday's nightly on Windows). It 
looked great to me!


On 4/23/2015 9:26 AM, Jared Wein wrote:

How was the performance when APZ + e10s was turned on the other day? I
imagine that will have a big impact on scrolling performance for treeherder
since it's a pretty heavy JS page.

On Thu, Apr 23, 2015 at 11:16 AM, Mike Hoye  wrote:


On 2015-04-23 10: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

  I asked some volunteers from the Reps to do an advocacy/evangelism

experiment last quarter: ask people to try Firefox for two weeks, see if
they stick with it, see what motivated them to switch back. Perceived
performance on Windows machines was one of the main reasons people went
back to Chrome. Scrolling jank was remarked on specifically.


- mhoye

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Treeherder UI performance much worse in Nightly vs Chrome

2015-04-23 Thread Jared Wein
How was the performance when APZ + e10s was turned on the other day? I
imagine that will have a big impact on scrolling performance for treeherder
since it's a pretty heavy JS page.

On Thu, Apr 23, 2015 at 11:16 AM, Mike Hoye  wrote:

> On 2015-04-23 10: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
>>
>>  I asked some volunteers from the Reps to do an advocacy/evangelism
> experiment last quarter: ask people to try Firefox for two weeks, see if
> they stick with it, see what motivated them to switch back. Perceived
> performance on Windows machines was one of the main reasons people went
> back to Chrome. Scrolling jank was remarked on specifically.
>
>
> - mhoye
>
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Treeherder UI performance much worse in Nightly vs Chrome

2015-04-23 Thread Mike Hoye

On 2015-04-23 10: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

I asked some volunteers from the Reps to do an advocacy/evangelism 
experiment last quarter: ask people to try Firefox for two weeks, see if 
they stick with it, see what motivated them to switch back. Perceived 
performance on Windows machines was one of the main reasons people went 
back to Chrome. Scrolling jank was remarked on specifically.



- mhoye
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Treeherder UI performance much worse in Nightly vs Chrome

2015-04-23 Thread Ed Morley
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
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform