i originally read this as “postmodern gcs” and got way too excited
-
-
-
"This is not a GC" Oh wait that's surrealism
End of conversation
New conversation -
-
-
Talks about 99th percentile. I hear
@giltene shaking his head in the background. -
Must admit I heard this first time from Gil and the hdr histogram library was super cool
- 2 more replies
New conversation -
-
-
Worth noting that the additional forwarding pointer requirements in Shenandoah have been minimised in recent builds; now the mark word space is reused when a GC and forwarding is needed only.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Part 1 is phenomenal as well
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Can’t get behind this claim though, 1ms is 75% of your deadline if doing audio with 256spls@192kHz and 1-2ms 99th percentile is a guaranteed glitch every 100 pauses, rendering your software unusable. 1-2ms is also quite a lot if your budget is <7ms (144Hz).pic.twitter.com/KEXK7VlO10
-
But unless you're running a real-time OS, you get pauses in that range even without a GC. Anyway, beating a GC on performance is easy if your object lifetime is very regular. When it isn't, like in most server apps, it's quite hard already, and the only real cost is footprint.
- 8 more replies
New conversation -
-
-
How did I not know about this blog. I just read https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e … and it's basically what I was thinking when Go were making that announcement.
-
Thanks for sharing.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.