|
@mathias | |||||
|
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…
|
||||||
|
||||||
|
V8
@v8js
|
3. sij 2019. |
|
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. |
|
Full credit to @leszekswirski for that cheesy punchline 🗑
|
||
|
|
||
|
Jan van Hellemond
@jvhellemond
|
3. sij 2019. |
|
Have all Enya jokes been made, or can I still squeeze one in? youtu.be/654tlKKI_Ys
|
||
|
|
||
|
Jesus Gonzalez◄
@gonzalezlrjesus
|
3. sij 2019. |
|
In my country Venezuela there is a river perhaps the most important one called Orinoco, causality? 🇻🇪😀
|
||
|
|
||
|
Segers Iƛn
@SegersIan
|
4. sij 2019. |
|
Great read! Loved it, does it make sense then to have provision 2 or more CPUs in a docker container/k8s pod environment for a node application? So it can leverage the concurrent/parallelism?
|
||
|
|
||
|
Peter Marshall
@hooraybuffer
|
4. sij 2019. |
|
V8 uses multiple threads for parsing, bytecode compilation, optimized code compilation and GC if they are available, so yeah, give us some threads! We probably won't use them at 100% though so up to you to decide on trade-offs there.
|
||
|
|
||
|
Marcus
@marcusklaas
|
4. sij 2019. |
|
love the URL!
|
||
|
|
||
|
Steven Roussey
@sroussey
|
4. sij 2019. |
|
I can't tell from the article, but I assume V8 will not need GC in cases where it can statically determine how to malloc/free, which would help relieve pressure on the nursery.
|
||
|
|
||