Lots of DOCSHELL GCs triggered for yahoo news raptor test
Categories
(Core :: JavaScript: GC, defect, P2)
Tracking
()
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
(Keywords: perf-alert)
Attachments
(2 files, 1 obsolete file)
132.44 KB,
text/plain
|
Details | |
1.12 KB,
patch
|
Details | Diff | Splinter Review |
I'm seeing a lot of DOCSHELL GCs when I run the yahoo news raptor tests with:
./mach raptor-test --test raptor-tp6-yahoo-news-firefox
I had a look at how this works and it seems that nsJSContext::MaybeRunNextCollectorSlice will start a new GC if the GC timer is pending (sGCTimer) as well as just running a slice.
I think the timer gets started when we close a page, so during benchmarks (and heavy use) this will often be the case. I think this may end up with us doing more GCs than necessary.
Assignee | ||
Comment 1•5 years ago
|
||
Test log with JS_GC_PROFILE enabled to show GCs.
Assignee | ||
Comment 2•5 years ago
|
||
This patch changes MaybeRunNextCollectorSlice so that it doesn't start a new GC/CC if one is not running already.
This reduces the number of GC slices when running the benchmark from ~400 to ~230.
Olli, what do you think? It seems to me that this is closer to the original intention of the code. I haven't run this through perfherder because I haven't worked out what try command I need to do this, but I figure that it won't make things worse.
Assignee | ||
Comment 3•5 years ago
|
||
Speedometer results seem unaffected on windows platforms. I'll try pushing this.
Comment 5•5 years ago
|
||
The priority flag is not set for this bug.
:jonco, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 7•5 years ago
|
||
== Change summary for alert #21587 (as of Tue, 25 Jun 2019 14:26:11 GMT) ==
Improvements:
3% raptor-stylebench-firefox windows10-64-shippable opt 44.40 -> 45.58
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=21587
Assignee | ||
Comment 8•5 years ago
|
||
The following performance regressions have been reported in bug 1565486:
2% raptor-sunspider-firefox linux64-shippable-qr opt 213.24 -> 218.23
2% raptor-sunspider-firefox linux64-shippable-qr opt 213.50 -> 217.40
3% raptor-stylebench-firefox windows10-64-shippable opt 44.40 -> 45.58
7% raptor-assorted-dom-firefox linux64-shippable-qr opt 26.71 -> 28.69
6% raptor-assorted-dom-firefox linux64-shippable opt 26.93 -> 28.47
5% raptor-assorted-dom-firefox linux64-shippable opt 27.13 -> 28.45
Based on that I'm going to back this out.
Assignee | ||
Comment 9•5 years ago
|
||
Assignee | ||
Comment 10•5 years ago
|
||
I guess we probably want to back this out of beta too.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 11•5 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1fbc711925ba
Please nominate for beta.
Assignee | ||
Comment 12•5 years ago
|
||
Comment on attachment 9077689 [details] [diff] [review]
backout1557771
Beta/Release Uplift Approval Request
- User impact if declined: Minor performance regressions.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a backout of a simple change and just returns the code to its original state.
- String changes made/needed: None
Assignee | ||
Comment 13•5 years ago
|
||
Comment on attachment 9077689 [details] [diff] [review]
backout1557771
Beta/Release Uplift Approval Request
- User impact if declined: Minor performance regressions.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a backout of a simple change and just returns the code to its original state.
- String changes made/needed: None
Beta/Release Uplift Approval Request
- User impact if declined: Minor performance regressions.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a backout of a simple change and just returns the code to its original state.
- String changes made/needed: None
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
NI Aryx to make sure this shows up on the radar for the next round of uplifts.
Comment 16•5 years ago
|
||
Not sure this is relevant, but the backout caused those changes:
== Change summary for alert #21888 (as of Mon, 15 Jul 2019 03:35:35 GMT) ==
Regressions:
3% raptor-stylebench-firefox windows10-64-shippable opt 46.04 -> 44.63
Improvements:
1% raptor-sunspider-firefox linux64-shippable opt 210.23 -> 207.64
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=21888
Comment 17•5 years ago
|
||
uplift |
Comment 18•5 years ago
|
||
Updated•5 years ago
|
Description
•