1388277 - Implement a process selector based on memory usage

Status: NEW

(Core :: DOM: Content Processes, enhancement, P2)

Description

[Gabor Krizsanits (INACTIVE)]

Currently we select process based on tab count, we should do something better. Either memory footprint or if it's possibly to measure memory fragmentation that can be another option.

Comment 1

[Mayank Bansal]

dupe of bug 1066789 or bug 1066792 ?

Comment 2

[Gabor Krizsanits (INACTIVE)]

(In reply to Mayank Bansal from comment #1)
> dupe of bug 1066789 or bug 1066792 ?

Not really.

Bug 1066789 is about moving away from an universal cap on the content process count.

Bug 1066792 is about an origin drive process selector.

Comment 3

[Jens Stutte [:jstutte]]

I assume that our recent fission work touched many options here and things are quite well tweaked these days (or at least for good reasons we have not much options left here) ?

Comment 4

[Randell Jesup [:jesup] (needinfo me)]

Actually, this is still relevant. Above 4 processes per eTLD+1 we start sharing processes, and choosing which one of the 4 to put it in could be smarter. Also, deciding when to share vs when to add another process could be better (than the current "new process if we have less than 4, else share"). If you have 40 massive google docs, 4 processes may be too few, and if you have 10 bugzilla tabs, you may be fine if they were all in 1 process.

This has been the source of major discussion in the fission group, and the current 4 processes-per-site was added late in the game since we didn't have anything smarter available to use.