Optimizing Node.js Performance: V8 Memory Management and GC Tuning, by @mcollina (@platformatic):

https://blog.platformatic.dev/optimizing-nodejs-performance-v8-memory-management-and-gc-tuning

1962

War Story: The Hardest Bug I Ever Debugged, by @jakevoytko:

https://www.clientserver.dev/p/war-story-the-hardest-bug-i-ever

Land Ahoy: Leaving the Sea of Nodes, by @v8js@x.com:

https://v8.dev/blog/leaving-the-sea-of-nodes

Rover 3500 (V8)

The Rover P6 series (named as the 2000, 2200, or 3500, depending on engine displacement) is a saloon car produced by Rover and subsequently British Leyland from 1963 to 1977 in Solihull, West Midlands, England, UK.

The P6 was the first winner of the European Car of the Year award.[2][3]...

https://en.wikipedia.org/wiki/Rover_P6

So I wrote some words about the LS-into-P5 saga so far, and I illustrated those words with some pictures. https://exhaust.lewiscollard.com/post/784450596/lewis-loses-the-plot/

Ended up next to a nice Rover P6 V8 the other day. Now you know what car the Princess' current wheel trims are from. P6 on the earlier trims, Princess on the later trims.

Malware Developers Increasingly Use V8 Javascript for Evasion | Cyber Insider
https://cyberinsider.com/malware-developers-increasingly-use-v8-javascript-for-evasion/ #Malware #V8 #Javascript

roses are red
violets are alive
let's shove an LS
in a Rover P5

Aston Martin Lagonda Series 3 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #automobile #european #history #old #new #classic #modern #luxury #sports #vehicle #transportation #engine #design #astonmartin #lagonda #fourdoor #saloon #british #1974 #1990 #645 #v8 #series2 #taraf #middleeast (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576366174

How does #V8's Orinoco garbage collector do compaction concurrently?

At first I thought that would require a read barrier, but then I realized that with a dynamic language like Javascript one can just replace each evacuated object with a proxy object that transparently forwards all accesses to the new object. The write barrier will catch any attempts to write new pointers to the block being evacuated. Such an approach couldn't work with full heap compaction, since objects need to be compacted into the space vacated by previously compacted objects, but it works perfectly fine with Orinoco's approach of evacuating blocks based on a fragmentation heuristic. It does mean the block can't be reused until the entire sweep phase finishes, though.

The same technique could theoretically be used to find and forward pointers from the old generation into the nursery, but that would mean the "from" space also couldn't be reused until the sweep phase completed. It's OK to delay reuse of evacuated blocks, because the system doesn't rely on those for new allocations, but it's not OK to delay swapping the spaces in the nursery. So Orinoco does need to use its write barrier to keep track of pointers from the old generation to the nursery.

The space overhead is far lower than for the train algorithm, but the tradeoff is the need to use free lists while moving objects out of the intermediate generation and evacuating old generation blocks, and a longer delay in freeing evacuated blocks. The train algorithm is always able to evacuate a block right away, and it never has fragmentation within blocks.

https://v8.dev/blog/trash-talk

Gonna hazard a guess and say this is probably a V8. #Photography #OldTruck #V8