3 ms·
The speedup sounds like it is very specific to GC, apparently the WebKit GC relies on this component heavily. I would guess this is relevant only for GC in Saf
by azakai 14y ago
The speedup sounds like it is very specific to GC, apparently the WebKit GC relies on this component heavily.
I would guess this is relevant only for GC in Safari, since it uses the WebKit JS engine, and not Chrome (which uses a completely different JS engine, V8).
It's also likely only a speedup in a specific GC benchmark. If it had helped in say the SunSpider benchmark, I'm pretty sure it would have been fixed a long long time ago.
- othermaciej 14y agoThis code is actually not that specific to GC - this particular spinlock is used by our custom malloc implementation. It's just that our GC creates a different concurrency pattern than most other workloads for the allocator.