Yeah -- I knew about the virtual heap arrays, so the GC explanation didn't make sense. I'll dig into it; thanks for the pointers.
I think you're right though. Once it's been running a while, it seems OK; so I think it was JIT compilation pauses.
I think you're right though. Once it's been running a while, it seems OK; so I think it was JIT compilation pauses.
It does indeed seem to be the JIT warming up. The good news is that Chrome Canary is significantly smoother, so 6-8 weeks until that hits stable.