|
@v8js | |||||
|
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:
v8.dev/blog/trash-talk pic.twitter.com/JAT8rHUeLI
|
||||||
|
||||||
|
Mathias Bynens
@mathias
|
3. sij 2019. |
|
Orinoco = @v8js garbage collection without the rubbish™
🚀 parallel
🏎 concurrent
🚤 incremental
Check out @hooraybuffer’s explanation of what that means: v8.dev/blog/trash-talk twitter.com/v8js/status/10…
|
||
|
|
||
|
Mathias Bynens
@mathias
|
3. sij 2019. |
|
Full credit to @leszekswirski for that cheesy punchline 🗑
|
||
|
|
||
|
Rich Trott
@trott
|
3. sij 2019. |
|
Any idea if anyone is still working on getting the idle garbage collection stuff into Node.js?
|
||
|
|
||
|
Peter Marshall
@hooraybuffer
|
4. sij 2019. |
|
Last I heard @apapirovski was going to look into it 😁
|
||
|
|
||
|
François Guthmann
@frguthmann
|
3. sij 2019. |
|
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.
|
||
|
|
||
|
Benedikt Meurer
@bmeurer
|
3. sij 2019. |
|
This is exactly what the idle time GC is about in @v8js
v8.dev/blog/free-garb…
|
||
|
|
||
|
Mike Greiling
@mikegreiling
|
3. sij 2019. |
|
|
||
|
Caio Lima
@caio_liima
|
4. sij 2019. |
|
|
||
|
Jan De Kock
@tjoener
|
5. sij 2019. |
|
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?
|
||
|
|
||