Closed
Bug 1223870
Opened 9 years ago
Closed 3 years ago
Microsoft Edge gets a +38.7% better score on Unity3D WebGL "Animation & Skinning" benchmark.
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P2)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jujjyl, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [gfx-noted])
+++ This bug was initially created as a clone of Bug #1223866 +++
STR:
1. Visit http://beta.unity3d.com/jonas/WebGLBenchmark/
2. Run the Animation & Skinning demo.
Observed:
Firefox 42 release gets a score of 199.
Edge 20.10240.16384.0 gets a score of 276.
Higher is better in this demo, so Edge gets a score 1.387x that of Firefox, or +38.7% better.
Reporter | ||
Comment 1•9 years ago
|
||
Geckoprofiler profile: http://people.mozilla.org/~bgirard/cleopatra/#report=9ef3dd1e6ff48c50ff5e1902e73ce7481776037c&invertCallback=true&filter=%5B%7B%22type%22%3A%22RangeSampleFilter%22,%22start%22%3A2575724,%22end%22%3A2586116%7D%5D&selection=%22(total)%22,1686
The profile here is similar to bug 1223866 and bug 1223869, and it is a some kind of mix of the two. JS side hotspots:
- 61.1% glDrawElements()
- 10.9% glBufferSubData()
- 4.3% glBindBuffer()
- 4.0% glUniformMatrix4fv()
Unlike the two other bugs, when factoring in native code as well, oddly 32.7% of total application execution time is in a single function rx::CopyNativeVertexData<int,3,3,0>(), followed by 11.1% in memmove, and 6.9% in rx::CopyNativeVertexData<float,4,4,0>().
Updated•9 years ago
|
Whiteboard: [gfx-noted]
Updated•6 years ago
|
Type: defect → enhancement
Priority: -- → P2
Comment 2•3 years ago
|
||
If I load the link http://beta.unity3d.com/jonas/WebGLBenchmark/ on the latest Nightly I get the following error: "An error occured running the Unity content on this page. See your browser's JavaScript console for more info. The error was: TypeError: WEBAudio.audioContext.listener.setVelocity is not a function."
Marking this as Resolved > Incomplete since the last activity on this issue was many years ago and it might not be relevant anymore. Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•