As a counter-proposal to #17503, we could improve STW times by performing stack re-scanning concurrently. I'm not actually proposing this, but I wrote a whole design doc before realizing a simpler approach would let us completely eliminate stack re-scanning. This issue is a place to put that design doc.
The text was updated successfully, but these errors were encountered:
Thanks for playing this out, @aclements. I agree that the approach in #17503 is much simpler—to understand, to reason about, to implement. The transitive mark write barrier seems like it would invite tail latency bugs, which would be hard to diagnose and to work around.