Closed
Bug 1989043
Opened 9 months ago
Closed 9 months ago
Reduce the number of parallel xpcshell tests on Windows to twice the core count
Categories
(Testing :: XPCShell Harness, task)
Testing
XPCShell Harness
Tracking
(firefox145 fixed)
RESOLVED
FIXED
145 Branch
| Tracking | Status | |
|---|---|---|
| firefox145 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(1 file)
In bug 1986407 I removed all the Windows specific limits to how many xpcshell tests we run in parallel. It seems that was a bit excessive as now the machines are under high load.
Here are some resource usage profiles:
- The machines have 8 logical cores
- Current state: 32 tests in parallel (+ 3 wasted cores by unrelated processes; getting fixed in the next Windows VM image) https://share.firefox.dev/4mhuxq3
- 32 tests in parallel (no more wasted cores, using the alpha fixed VMs): https://share.firefox.dev/4n1qH5G
- 12 tests in parallel: https://share.firefox.dev/48m4nzc (no longer at 100% CPU use)
- 16 tests in parallel: https://share.firefox.dev/46FPiHo (I think going ahead with this would be reasonable)
In these profiles, look for the new "Sampling Interval" track that indicates how long it took for resourcemonitor.py's 100ms timer to be fired. That's a good proxy for how much load the machine is receiving.
Whether we should include that "Sampling Interval" track in the resource monitor by default to make future similar troubleshooting easier is an open question. I'm leaning towards 'yes'.
| Assignee | ||
Comment 1•9 months ago
|
||
Pushed by fqueze@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/1d3bfe7467e2
https://hg.mozilla.org/integration/autoland/rev/7243bd713cbc
Reduce the number of parallel xpcshell tests on Windows to twice the core count, r=jmaher.
Comment 3•9 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
status-firefox145:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 145 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•