5 ms·
Speaking about GC behavior of other benchmarks: 1) one with Buffers is also causing mark-sweep/compact pauses (7-15ms each) because Buffer constructor calls Ad
by mraleph 16y ago
Speaking about GC behavior of other benchmarks:
1) one with Buffers is also causing mark-sweep/compact pauses (7-15ms each) because Buffer constructor calls AdjustAmountOfExternalAllocatedMemory which triggers full gc cycle if it thinks that too much memory is held outside V8.
2) GCs in string based benchmark are mainly scavenges taking 0 ms plus < 10 full collections taking <6ms each on my desktop.
That is all I can say. V8 GC is performing well here from my point of view.
- hannesw 16y agoI just found out the same. So I guess it must be some intra-VM data shifting? Anyway, I'll update my posting accordingly.