Hacker News Reader

Comment by skar | Hacker News Reader

I'm getting 60 fps approximately for the spinning cube with chrome 6 on Ubuntu Lucid and my laptop has a core i3 with built in arrandale based GPU, not an nvidia or ati one.

Not long ago, on an older laptop, I was getting the same fps for native Linux apps. Seems browsers are acquiring native capabilities, but at a faster rate :)

View on HN

It seems to be capped at 60FPS. But it's the simplest demo, my results for the others are nowhere near 60FPS, most aren't even usable unfortunately.

I get 1FPS on the terrain generation one. Still cool :)

I suspect you're using MacOS? Chrome/Safari on MacOS perform horribly slow on some of these demos. CoreGraphics seem to be the culprit.

For some reason I'm getting horrible crashes on my app (has worked great for months. Still works great on Linux and Windows) since chrome switched to gpu rendering for everything. I haven't found the issue yet but it's really odd.

Did you already try to update GPU driver?

I had really bad crashes (high pitch noise, bright white flash, driver killed) on Firefox 4 and Chrome 7 when they started to use HW acceleration and problems went away after the update.

Though this was on Windows 7, no idea about OSX.

No luck on that, I checked and there was in fact a graphics update but that didn't affect the behavior. My next step is to try to figure out what is causing it to make a bug report.

None of them seem usable on firefox.

Oh, most of them are, but the ones with textures seem to be awfully slow (the earth one for instance). Works nice in chromium though.

I guess that has to do with hardware acceleration. FF3.x does not have that yet, so it's falling back to software rendering SVG's, and software rendering is.. you know, awfully slow.

Try the FF4 beta if you want to see how things shape up, I think that has HW acceleration built in, though I'm not sure how far they are with WebGL.

I think they could improve the speed if they used webworker

fwiw, i managed 61 fps on a karmic machine w/ i7.

and out of curiosity i tried a froyo powered device (droid 2.2) and got up to 26 fps.

I really only glanced at the code so I could be wrong here. But it appeared to me as though the main loop was written with something like, 1000 / 60, which was probably intended to cap at 60fps.

If you took that code and modified the loop to run more frequently, do you get even better performance?

The 'Example's section aren't using your GPU, they're all using CanvasRenderer it seems.

Reply on news.ycombinator.com