Closed Bug 1096321 Opened 10 years ago Closed 7 years ago

Treeherder is painstakingly difficult to use with e10s enabled

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
major

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s + ---

People

(Reporter: RyanVM, Unassigned)

References

(Blocks 1 open bug)

Details

On my company-issued W530 laptop w/ 24GB of RAM, quad core CPU w/ hyperthreading, etc, I see very long lag times switching between Treeherder tabs. I'll get an empty content area for multi-second delays, which adds up to a big productivity hit when trying to actively sheriff the trees.
It's less of an issue when I increase the number of content processes to match or exceed the number of treeherder tabs opened. Each TH tab then ends up in its own process, so everything isn't lagged out by some tabs fetching and displaying new job data.
Blocks: 1112352
Treeherder performance hasn't been problematic w/ e10s enabled for quite some time.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.