Closed
Bug 1543017
Opened 5 years ago
Closed 5 years ago
Running JS tests on a remote machine generates 400KB/s network traffic
Categories
(Core :: JavaScript Engine, task, P5)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
Details
Attachments
(1 file)
I was surprised to see such a large amount of network traffic while running jittests/jstests.
Assignee | ||
Comment 1•5 years ago
|
||
ProgressBar has an update_granularity() method but there's nothing to ensure that poke() doesn't get called more often than this, and this is what is happening.
Assignee | ||
Comment 2•5 years ago
|
||
Don't update the progress bar more than necessary by recording the last update time and checking in poke(). Network traffic is down to 12KB/s with this patch.
Comment 3•5 years ago
|
||
But but but I was using this for space-heater functionality! https://xkcd.com/1172/ (hovertext)
Pushed by jcoppeard@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/16070c339499 Don't update test progress bar so often r=sfink
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•