[helpbygrace]

Wow, after viewing the examples, almost 10% battery was consumed.

[unconed]

... but it's still more efficient than pure JavaScript, asm or not. And so much faster than MathBox 1.

[pizza]

Some probably helpful debugging questions to ask:

Laptop or mobile? How much time did you spend watching the examples? What is your battery's storage capacity (milliamp-hours, usage hours, etc.)? Does it have a GPU? CPU usage? Is that battery drain consistent w/ other things that use that amount of CPU? etc.

[helpbygrace]

I'm using 2013 late rMBP 13inch .

[z-e-r-o]

Totally agree, under Chrome / OS X, fans went crazy on my rMBP 15 iGPU and CPU raised 80 C degrees just to watch a few slides of that site. I closed the tab to stop overheating.

[MBCook]

Huh. I use Safari / OS X on a 4 year old MacBook Pro. I keep it locked on the integrated CPU and it worked fine, barely increasing the system load. Only one or two of the effects near the end made any noticeable difference.

Of course you're pushing 4x as many pixels as me.

Try Safari (you have to enable WebGL in the Develop menu). I wonder it's a Chrome issue.

[girvo]

Safari on my rMBP 13" did the same thing, heh. Still worth it. Amazing work.

[PudgePacket]

Ran completely fine on my 13" air.

[socialist_coder]

Well, it's about 3D graphics. What do you expect?