<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - GC should be concurrent"
href="https://bugs.webkit.org/show_bug.cgi?id=149432">149432</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GC should be concurrent
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Other
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>JavaScriptCore
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>fpizlo@apple.com
</td>
</tr></table>
<p>
<div>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>