Closed
Bug 852578
Opened 11 years ago
Closed 7 years ago
Minesweeper benchmark incredibly slow
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: scoobidiver, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: perf, Whiteboard: [ietestdrive])
Attachments
(3 files)
This table is explicit. It's at least seven times worse than IE 10. IE 10 Checker Island Nightly/20130318: 17.2 sec 112.1 sec 29.6 sec Chrome 25: 5.8 sec 29.3 sec 9.8 sec IE 10: 2.5 sec 5.5 sec 4.2 sec
Comment 1•11 years ago
|
||
Can we get a profile of this?
Comment 2•11 years ago
|
||
I get different Results: IE 10: Trunk ~ Chrome 27 = 5s Checker: Trunk ~ Chrome 27 = 26s Island: Trunk ~ Chrome 27 = 7,6s on a ATI Radeon HD 4850 with default HWA Settings on Win 7 with Platform Update. Btw, [parity-xy] is used for Features, not Perf.
Whiteboard: [ietestdrive][parity-chrome][parity-ie10] → [ietestdrive]
Reporter | ||
Comment 3•11 years ago
|
||
My graphics section of about:support is: Adapter Description Mobile Intel(R) 4 Series Express Chipset Family Adapter Drivers igdumd64 igd10umd64 igdumdx32 igd10umd32 Adapter RAM Unknown ClearType Parameters Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 100 Device ID 0x2a42 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16492) Driver Date 10-4-2012 Driver Version 8.15.10.2869 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 10 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 4 Series Express Chipset Family) AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo With HW acceleration turn off, it's worse with a ratio of 1.5 (28 sec, 181 sec, 44 sec).
Reporter | ||
Comment 4•11 years ago
|
||
Reporter | ||
Comment 5•11 years ago
|
||
Reporter | ||
Comment 6•11 years ago
|
||
Comment 7•11 years ago
|
||
Can you profile using the Gecko profiler add-on and upload the result using the share button on the bottom right?
Reporter | ||
Comment 8•11 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #7) > Can you profile using the Gecko profiler add-on and upload the result using > the share button on the bottom right? The add-on doesn't show any toolbar or button so I can't use it.
Comment 9•11 years ago
|
||
Did you get it from here? https://github.com/bgirard/Gecko-Profiler-Addon/raw/master/geckoprofiler.xpi
Reporter | ||
Comment 10•11 years ago
|
||
The one from AMO doesn't work. With the Github's one: * IE 10: http://people.mozilla.com/~bgirard/cleopatra/#report=0f8dbe347a5898d96381af3f5d0a99f860a5dfc0 * Checker: http://people.mozilla.com/~bgirard/cleopatra/#report=bb0e6e149202c5b79f10e3e65c2f53074b2dbc88 * Island: http://people.mozilla.com/~bgirard/cleopatra/#report=c5d230a33af6dae433d6eb9906c2f1111f12517b
Comment 11•11 years ago
|
||
It looks like we're being hurt a lot by GDI interop. It would be worth trying this build to see if it helps: https://tbpl.mozilla.org/?tree=Try&rev=d1921bda6a6a
Reporter | ||
Comment 12•11 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #11) > It would be worth trying this build to see if it helps: > https://tbpl.mozilla.org/?tree=Try&rev=d1921bda6a6a I don't find it in ftp://ftp.mozilla.org/pub/firefox/try-builds/
Comment 13•11 years ago
|
||
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/jmuizelaar@mozilla.com-d1921bda6a6a/try-win32/
Reporter | ||
Comment 14•11 years ago
|
||
With the try build, it's slightly better: * IE 10: 15.2 seconds http://people.mozilla.com/~bgirard/cleopatra/#report=7dfa07a47f5b28981957c24ad7ec50aba140d2b9 * Checker: 94.2 seconds http://people.mozilla.com/~bgirard/cleopatra/#report=91487277b8dc4ee2fe7cd7fc36a7048b00c44489 * Island: 23.3 seconds http://people.mozilla.com/~bgirard/cleopatra/#report=66fd640abed543a92d023deef1192fcfcd58de26
Comment 15•11 years ago
|
||
Hmm.. we're still getting hurt by the texture creation locks. I think we probably need to be creating less textures.
Updated•11 years ago
|
Blocks: ietestdrive
Comment 16•11 years ago
|
||
Windows 7 with HWA, on the IE10 map Nightly 27 - 6.50s Chrome 29 - 6.60s IE 10 - 4.70s On Checker Nightly 27 - 34.10s Chrome 29 - 39.00s IE 10 - 13.20s
Comment 17•7 years ago
|
||
On the same hardware from years ago: Huge Checker Firefox 54 - 33.20s Nightly (Advanced Layers on) - 28.30s Chrome 59 - 32.90s IE 11 - 4.30s (!!)
(In reply to Guilherme Lima from comment #17) > On the same hardware from years ago: > > Huge Checker > Firefox 54 - 33.20s > Nightly (Advanced Layers on) - 28.30s > Chrome 59 - 32.90s > IE 11 - 4.30s (!!) Do you have the numbers for nightly with advanced layers off? layers.mlgpu.dev-enabled and layers.mlgpu.enable-on-windows7 set to false in about:config and Firefox restarted.
Comment 19•7 years ago
|
||
Tested again today: Nightly (Advanced Layers on) - 28.30s (exactly same number from yesterday, nice!) Nightly (Advanced Layers off) - 30.60s
David, let's make sure this is expected regression.
Flags: needinfo?(dvander)
Comment 21•7 years ago
|
||
It's an improvement... it takes less time to complete.
I ran it locally, got the same improvement, and still read it as a regression. And it's still early in the day :)
Flags: needinfo?(dvander)
Although, the "Island" one does regress for me, ~10% or so...
I see a slight improvement on all 3 on my machine, but I can't tell what this benchmark is actually measuring. It doesn't look like anything. Maybe it was supposed to measure Canvas 2D and now instead is testing whether setTimeout is implemented the same as Edge.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•