Hacker News Reader

Comment by jejones3141 | Hacker News Reader

The "more details" link goes to a blog post from September 2010, so I suspect the test has been around for a while, but it was still interesting to see that for me (Linux, nVidia 560Ti, 319 proprietary driver), Firefox reported 60+ fps while Chrome reported 24 fps.

View on HN

Jejones, you're lucky. I got 20 fps, but after some tuning I get 42 fps, which is the answer to the universe and all =)

Here's how you double performance on Chrome:

Open chrome://flags then enable:

     *  #ignore-gpu-blacklist
     *  #force-compositing-mode-2
     *  #enable-experimental-canvas-features
     *  #accelerated-filters
     *  #enable-css-shaders

Optional Rendering Tweaks:

    *  #impl-side-painting
    *  #enable-webgl-draft-extensions

TCP/IP Tweaks that work:

    *  #enable-quic-https
    *  #enable-spdy4a2
    *  #enable-http2-draft-04
    *  #enable-async-dns
    *  #enable-tcp-fast-open

This is handy when you use OneTab, Tabs close much faster this way:

    *  #enable-fast-unload

Guess I'll have to turn them on one at a time; when I twisted all the knobs, nothing with flash would work.

Reply on news.ycombinator.com