Orinoco = @v8js garbage collection without the rubbish™
parallel
concurrent
incremental
Check out @hooraybuffer’s explanation of what that means: https://v8.dev/blog/trash-talk https://twitter.com/v8js/status/1080867305532416000 …
Orinoco (V8’s garbage collector) evolved from a sequential stop-the-world implementation into a mostly parallel and concurrent collector with incremental fallback. @hooraybuffer talks trash:
https://v8.dev/blog/trash-talk pic.twitter.com/JAT8rHUeLI
-
-
-
Full credit to
@leszekswirski for that cheesy punchline
End of conversation
New conversation -
-
-
Any idea if anyone is still working on getting the idle garbage collection stuff into Node.js?
-
Last I heard
@apapirovski was going to look into it
- 3 more replies
New conversation -
-
-
Awesome! I kind of wish we could explicitly tell the browser we're done with a frame though. Like if I'm calling RAF, please do whatever you want with CPU until next frame, including GC.
-
This is exactly what the idle time GC is about in
@v8js https://v8.dev/blog/free-garbage-collection … - 3 more replies
New conversation -
-
-
- 2 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Ah concurrent mark sweep, caught up to Java I see
. Congrats on the implementation. Now next step is (almost) zero pause time gc. Any of these in the pipeline? - 2 more replies
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.