[Webkit-unassigned] [Bug 149432] New: GC should be concurrent

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=149432

            Bug ID: 149432
           Summary: GC should be concurrent
    Classification: Unclassified
           Product: WebKit
           Version: Other
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: fpizlo at apple.com

Our GC is parallel and generational. That's great for throughput, but it's pretty bad for pause times. The JetStream/splay-latency test is one great example of how bad our pause times are.

We can make our GC incremental or even concurrent. The following things can be concurrent:

- Marking. We can use an incremental update barrier that re-greys anthracite objects as we store into them.
- Copying. We can use Baker's barrier at GetButterfly. We may be able to avoid using barriers if we load a butterfly only to load from it before any other side-effect.
- Sweeping of blocks that don't have destructors.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150921/b082a65d/attachment.html>