Closed Bug 718791 Opened 14 years ago Closed 14 years ago

[CC] Extra slow CC when other cores are busy?

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mccr8, Unassigned)

Details

Patrick has noticed that when he's building something, his CC times get really long. After he mentioned that, I've noticed a bit of that myself when I'm running CC log analysis scripts (but not while compiling). I wonder if something like this could happen because of the separate CC thread? I could imagine that the main thread gets put on its own core, so if the CC ends up getting put on another core, then there's some CPU intensive thing running there, then the CC starts up on the busy thread, but gets lower priority, that the CCs will be long. Patrick said that on OSX the main thread may get higher priority because it is an IO thread or something. Might be worth measuring at least.
Could also be saturating the memory bus.
That would probably affect the GC as much as the CC, though, right? Well, maybe each core has different.. buses. or something.
Yeah, I would expect it to affect the gc too.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.