Comments on: HTML5 Performance Testing

By: thristhart

thristhart — Fri, 27 Apr 2012 00:41:01 +0000

I had 30fps in average but every like 5 seconds it would hang for about 200 milliseconds, making it feel very laggy overall.

By: PoV

PoV — Thu, 26 Apr 2012 23:03:28 +0000

New build(s) are up. Both include the results of some profiling, and a different way of framerate synchronizing. They should run much better, but however Chrome likes to FREAK OUT as it starts, running a crappy framerate for a while, before finally calming down and working properly.

By: PoV

PoV — Thu, 26 Apr 2012 22:56:13 +0000

Thanks for the link. Yes, this especially made Chrome work better. Thanks for the tip.

By: moop

moop — Thu, 26 Apr 2012 20:00:30 +0000

I got 29-31fps running in Chrome/Win7 on an AMD Phenom II X4 965 (quad core, 3.4ghz) with 4gig of RAM, Radeon HD 4890 GPU. I saw intermittent long (100-300ms) stalls but additionally the game felt a little sluggish making it difficult to judge the timing for walljumps.

By: Thinkofdeath

Thinkofdeath — Thu, 26 Apr 2012 19:37:57 +0000

Have you looked at using requestAnimationFrame instead of setInterval? It might give you better performance. (http://paulirish.com/2011/requestanimationframe-for-smart-animating/)

By: bluescrn

bluescrn — Thu, 26 Apr 2012 19:33:08 +0000

The ’60fps’ version runs at around 22fps in Firefox 11 on my 2008 Macbook 13″ (Core 2 Duo 2.4Ghz) – which runs most Flash and Unity stuff pretty well.

IMHO, HTML5 isn’t ready for gaming yet. Flash may be dying, but there isn’t a viable replacement yet

There’s absolutely no excuse for an ‘Amiga-esque’ lo-res pixel-art game not running at 60fps on a multi-GHz PC, unless it’s simply built on top of bad/unsuitable technology.

By: PoV

PoV — Thu, 26 Apr 2012 18:37:27 +0000

Okay, I made a version of the game that runs at 60 FPS, removes my “floating camera” that everyone hates so much, and some other things. See above.

By: EricTheCoolDude

EricTheCoolDude — Thu, 26 Apr 2012 17:43:26 +0000

I don’t think it’s a performance problem, I think it’s that the scrolling feels choppy because the pixels are so big and it’s always proportional.

By: Codexus

Codexus — Thu, 26 Apr 2012 17:10:23 +0000

25-30 average on Firefox. The problem isn’t that much the average than the occasional stutter. It seems smoother on Chrome but it’s displayed really tiny so of course it runs better.

By: 7Soul

7Soul — Thu, 26 Apr 2012 17:07:00 +0000

27~30 on chrome. It seems as the game is lagging at all times

By: lexaloffle

lexaloffle — Thu, 26 Apr 2012 17:01:10 +0000

I get 30 under firefox 11.0/ubuntu. But! It doesn’t feel very consistent though.. I’d say it sometimes slows down to around 10fps for 3-4 frames every now and then, but without and change in the reported framerate.

By: Spiridios

Spiridios — Thu, 26 Apr 2012 16:35:10 +0000

Looks like a neat game, but I’m at work so I’ll just report my numbers and play later. =p The game starts out at 30fps, but dipped to 25/28 range a couple of times. The graphics and scrolling seemed a little jittery/slow. It’s not much, but it’s noticeable. Could it be that 30 fps is too low for this kind of game? This was on both Firefox 12 and Chrome 18 on win7 64 with an Intel Core i5-2500 @ 3.3Ghz.