← Back to context

Comment by perennialmind

3 days ago

Dotnet's GC has a real latency problem. Miguel de Icaza gave a nice talk on why noticeable pauses are inevitable in a stop-the-world tracing GC, proposing Swift's reference-counting GC as the viable alternative [1]. Still, there are recent developments (Satori GC) with the promise to make the worst case far more palatable (e.g. 250ms -> 5ms) [2].

[1] https://www.youtube.com/watch?v=tzt36EGKEZo

[2] https://github.com/dotnet/runtime/discussions/115627#discuss...