WebGL has more cpu utilization than canvas on this

Bugs will be moved here once resolved.

Post » Mon Aug 19, 2013 8:19 pm

Link to .capx file (required!):
Open Lighting.capx on the C2 examples.

Steps to reproduce:
1. Test with debugger on Chrome and move the cursor around.
2. Try both canvas2d and WebGL and observe CPU utilization.

Observed result:
Cpu utilization with Chrome on WebGL is much higher (20%) than canvas2d (0-1%) even with a fast cpu.


Expected result:
At least the same performance than canvas2D or better.

Browsers affected:
Chrome: yes
Firefox: no
Internet Explorer 11 Preview: no

Operating system & service pack:
Tested on:
Windows 7 Prof. 64 bits
Windows XP 32 bits

Construct 2 version:
Tested on:
r141 beta
r139 stable
B
75
S
29
G
17
Posts: 256
Reputation: 15,250

Post » Tue Aug 20, 2013 12:37 am

Closing as won't fix. The CPU usage is not a very scientific value - just a rough estimate, as best as can be measured from javascript which typically cannot access the real operating system measurement. In WebGL mode the engine is likely doing the same or less work, but rendering calls are included in the CPU time; in canvas2d mode the browser makes the rendering calls, so are probably not included in the CPU time. Other benchmarks show that WebGL mode is almost always faster than canvas2d mode, so I think this explanation suffices.
Scirra Founder
B
402
S
238
G
89
Posts: 24,632
Reputation: 196,031


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 3 guests