title: Why would Chrome cap frame rate at 30fps?
body: <p>I'm doing some d3.js visualization development (mostly SVG) and I was measuring the FPS of my transitions using the "Show FPS meter" option in the web tools.  Strangely, the FPS appears to be capped at exactly 30fps.  Other colleagues using the same version of Chrome consistently get 60fps running the same code.</p>
  
  <p>I can get a higher frame rate out of other browsers and out of Flash so it seems to be something Chrome specific.</p>
  
  <p>Does anybody know what kinds of things might cause Chrome to clamp the frame rate at 30fps?  I've read that it might do this if it thinks that a smooth 30fps will look better than a choppy 60fps if there is a lot of variance, but I don't understand why it would need to do that on my fast desktop machine.</p>
  
  <p>Here's an example page that shows the problem:</p>
  
  <p><a href="http://mbostock.github.io/d3/talk/20111018/collision.html" rel="nofollow">http://mbostock.github.io/d3/talk/20111018/collision.html</a></p>
  
  <p>Drag your mouse around and you'll probably see the FPS counter sit around 60fps.  On my machine, it sits at precisely 30fps.</p>
  
  <p>I've tried Canary with the same results.</p>