Open
Bug 1448895
Opened 7 years ago
Updated 2 years ago
Mouseover on https://bgrins.github.io/xbl-analysis/graph/ graphs is very slow
Categories
(Core :: Graphics: Canvas2D, defect, P3)
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: perf, Whiteboard: [gfx-noted])
Attachments
(1 file)
26.48 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180325220121
Steps to reproduce:
1. Create new profile on nightly
2. Open https://bgrins.github.io/xbl-analysis/graph/
3. Scroll down to the bottom-most graph
4. Mouse-over the graph
Actual results:
the pop-up with info in very slow to render
Expected results:
not so
https://perfht.ml/2umnyrd
Reporter | ||
Comment 1•7 years ago
|
||
profile with webrender enabled: https://perfht.ml/2umVuUM
It feels about the same as with WR disabled
Reporter | ||
Updated•7 years ago
|
Comment 2•7 years ago
|
||
Bas, can you make sense of the profile? Looks like we're just spending a lot of time inside D2D filling things, but that doesn't look out of the ordinary. Should we expect a case like this to be slow in D2D canvas?
Flags: needinfo?(bas)
Keywords: perf
OS: Unspecified → Windows 10
Priority: -- → P3
Hardware: Unspecified → x86_64
Whiteboard: [gfx-noted]
Comment 3•7 years ago
|
||
(In reply to Lee Salzman [:lsalzman] from comment #2)
> Bas, can you make sense of the profile? Looks like we're just spending a lot
> of time inside D2D filling things, but that doesn't look out of the
> ordinary. Should we expect a case like this to be slow in D2D canvas?
Based on the profile it looks like some type of complex clip is playing a role here. But we may be excessively pushing/popping that clip or something along those lines. Fwiw this performs -much- better in Edge, so obviously there's something we can do better here!
Flags: needinfo?(bas)
Reporter | ||
Updated•5 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 4•3 years ago
|
||
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Comment 5•2 years ago
|
||
This has improved significantly: https://share.firefox.dev/425LOZR (150ms per tick. previously it was 250ms per tick)
Chrome however is really fast here now
You need to log in
before you can comment on or make changes to this bug.
Description
•