Closed Bug 1014409 Opened 10 years ago Closed 9 years ago

PJS GC: Use common chunk pool when possible

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: lth, Unassigned)

References

Details

Currently the PJS GC has its own chunk pool, hanging off of ThreadPool.  This is expedient and performant but may retain too much memory and also does not share unused memory with other parts of the system.

We could use the GC's chunk pool but it probably does not (currently) have the performance characteristics we want and is not (currently) tunable.  Investigative item: see if the GC's chunk pool can be adapted easily to our purposes.

We should use the per-process chunk pool (bug 988356) if and when that becomes available.  I've filed some requirements on that bug.
Assignee: lhansen → nobody
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.