<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT-M] WebGL (Auqarium/ Dynamic Cubemap /Toon-Shading) performance on firefox hugely slower than chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=75140#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BYT-M] WebGL (Auqarium/ Dynamic Cubemap /Toon-Shading) performance on firefox hugely slower than chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=75140">bug 75140</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to <a href="show_bug.cgi?id=75140#c4">comment #4</a>) > (In reply to <a href="show_bug.cgi?id=75140#c3">comment #3</a>) > > By check "about:config", > 1."Use hardware acceleration where available" is enable. > 2.layers HW:layers.acceleration.disabled (defult). You could try: webgl.force-enabled=true layers.acceleration.force-enabled=true > "intel_gpu_top" show render busy:9%-15% when run the case. Pressing "1" in "top" lists CPU utilization for each core separately. If FF limited by CPU utilization? If that happens also with layers HW acceleration, I think this is FF issue, not Mesa one. Firefox just isn't using GPU. To verify that it's not a Mesa issue, you could do (as root): perf record -a ^C (after half a minute) report report -n -s dso To see what is using most CPU in the benchmark. (Note: perf results are valid only if process is using all CPU as perf record is counting only active cycles, not idling (e.g. waiting for GPU), i.e. check first from "top" that use-case is really CPU bound.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>