Bug 129090 – WebGL EXT_disjoint_timer_query may now be implemented

• Status: RESOLVED
• Resolution: FIXED
• Component: WebGL

[Florian Bösch]

The WebGL extension EXT_disjoint_timer_query was moved to draft: http://www.khronos.org/registry/webgl/extensions/EXT_disjoint_timer_query/

Vendors are encouraged to consider implementation of this extension.

[Florian Bösch]

Chrome ticket: https://code.google.com/p/chromium/issues/detail?id=345227
Firefox ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=974832

[Florian Bösch]

This extension can be implemented by a UA if either any one of these conditions is met:

- The OpenGL 3.3 core profile is supported: https://www.opengl.org/registry/doc/glspec33.core.20100311.pdf
- ARB_timer_query is supported: https://www.opengl.org/registry/specs/ARB/timer_query.txt
- Direct3D 9 is supported: http://msdn.microsoft.com/en-us/library/windows/desktop/bb147308(v=vs.85).aspx
- The OpenGL ES EXT_disjoint_timer_query is supported: http://www.khronos.org/registry/gles/extensions/EXT/EXT_disjoint_timer_query.txt

The disjoint behavior lacking from ARB_timer_query and OpenGL 3.3 core can be emulated by the UA.

[Florian Bösch]

The ANGLE project ticket possible used for tracking this feature: https://code.google.com/p/angleproject/issues/detail?id=142

[Florian Bösch]

Any possibility that the iOS8 driver could be updated to include a way to support timer queries?

ES 3.0 doesn't contain timer queries, and the EXT_disjoint_timer_query extension is not listed for the iPad mini retina (PowerVR SGX543MP2) or iPod touch 5th gen (PowerVR SGX543MP2).

EXT_disjoint_timer_query is listed natively for the Nexus 4/Nexus 7/Asus PadFone X (Qualcomm Adreno 320), Nexus 5/Samsung SM-G870 (Qualcomm Adreno 330). The Xiamoi Minipad (NVIDIA Tegra) supports ES 3.1 which has timer queries.

Since the SGX543MP2 is a pretty powerful chip, it seems plausible to me the capability could be there in hardware.

[Florian Bösch]

EXT_disjoint_timer query is desperately needed. Measuring performance by way of FPS is completely unusable, as it mostly just boils down to 3 answers, 15fps, 30fps or 60fps. Programmers can't measure their WebGL programs, and hence they cannot optimize them. This is extremely bad.

[Marcin Ignac]

Is there any chance of this being implemented? It has been shipped in Chrome and FF long time ago..

[Radar WebKit Bug Importer]

<rdar://problem/30054979>

[EWS]

Committed 260367@main (dad993a38b59): <https://commits.webkit.org/260367@main>

Reviewed commits have been landed. Closing PR #10140 and removing active labels.