Closed Bug 702263 Opened 13 years ago Closed 12 years ago

[CC] Optimize CC based on NS_SUCCESS_INTERRUPTED_TRAVERSE

Categories

(Core :: XPCOM, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 705582

People

(Reporter: smaug, Unassigned)

References

Details

Attachments

(1 obsolete file)

Right now NS_SUCCESS_INTERRUPTED_TRAVERSE just reduces some traversing.
But I think we could use that information to mark objects as black.

Or am I missing something important?
Attached patch wip (obsolete) — Splinter Review
I was thinking something as simple as this.
Don't you need to flood?
Yes, you need to flood.  But that will be a little weird because we are in the middle of traversal.

Olli, what is the goal here?  Is it to reduce the size of the graph or reduce the number of nodes that are traversed?  The actual color marking phase doesn't seem to take much time.
Optimize CC somehow :)

We know that something is black, but we don't use that information in anyway.

As peterv said on IRC, it would be better if we wouldn't even add the known-to-be-black nodes to
graph. But that is trickier and I trying to figure out if there are some low hanging fruits here...
Attachment #574289 - Attachment is obsolete: true
I feel like we should do something that makes use of this information, but I'm not sure what we can do. :)
Olli, is this basically a dupe of bug 705582 or is there something separate here?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: