We worked hard to make it fast in Chrome. Their profiling tools were great at finding some bottlenecks that improved perf in all browsers.

My guess is that we're pushing up against the limits of Chrome's repaint rate when the map canvas starts cranking. That's not as much of a bottleneck in Firefox since there's not a separate rendering process.

It's much faster on Chrome than Firefox here (ubuntu).