Closed Bug 864943 Opened 7 years ago Closed 6 years ago

[meta] Reduce the amount of chrome JS we run in B2G

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: justin.lebar+bug, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c=memory p= s=2013.12.06 u=] [MemShrink:P2])

Attachments

(3 files)

Chrome JS is one of the largest consumers of memory in B2G.  Leaving aside B2G's worker threads (bug 864927, bug 864931, bug 864932), we spend about 8mb of memory on chrome JS in the B2G main process.

We ought to look at reducing the amount of JS we run in the main process, in an attempt to reign in our memory usage.  We can use this bug for investigation and then spin off concrete pieces of action into blocking bugs.
In this memory report, JS uses ~2x as much memory, but at least you can see where it's going.  I have no idea how representative this report is.

A better approach would be to try b2g on trunk with zones enabled and jsloader.reuseGlobal set to false.
Whiteboard: [MemShrink] → [MemShrink:P2]
Depends on: 870676
Depends on: 913343
No longer depends on: 913343
Keywords: perf
Whiteboard: [MemShrink:P2] → [c=memory p= s= u=] [MemShrink:P2]
Rolling dependencies up into Bug 797189 (Operation Slim-Fast), and closing this one out as it's very broad and doesn't look like it's caught on as an active meta. Resolving as INCOMPLETE for lack of a better option.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [c=memory p= s= u=] [MemShrink:P2] → [c=memory p= s=2013.12.06 u=] [MemShrink:P2]
You need to log in before you can comment on or make changes to this bug.