[sfink]

That sounds great. But as someone who works on the Firefox GC team, I gotta say: what?

Or more specifically, I'm wondering what change you could be referring to. We've had incremental GC for many years now, which does exactly what you describe. It's true that we keep splitting up more of the uninterruptible pieces into smaller chunks, but I don't recall any major change there recently. (I'm not very good at marketing, am I?)

And according to telemetry, the incremental slices have been working quite well for most people, at least within the last dozen releases or so. We have a budget, and it's rare that we go over it. Not that I fully trust telemetry; if you have counterexamples please file a bug. (I'd love to have a nice set of scenarios that are problematic for the GC. Our telemetry errs strongly on the side of privacy, as it should, so I can't get URLs automatically.)

[kaba0]

May I ask you about the “big picture” of how Firefox’s GC work? How does it compare to something like OpenJDK’s ZGC?

[whatshisface]

It might not have been that recent. Incremental GC was not new in the patch, what changed was the tuning. It happened some time in the last six months and was a huge improvement for the use case of realtime rendering. At the time I was comparing performance between release and nightly, and it was night and day.