Closed Bug 525116 Opened 16 years ago Closed 14 years ago

TM: let a different thread than the main thread run the GC

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: gal, Unassigned)

Details

Currently the main thread runs the GC. All other threads wait. As a result the thread with the most performance-critical code running has to trash its cache and stream through the entire heap to mark and sweep. Instead, we should let some other thread (or a GC thread) run the GC and preferably pin it to some other core.
I'm going to assume that the GC work done in the last two years has superseded this bug. Please reopen if that's not the case.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.