Thanks for reporting this.
Assignee: nobody → general
Product: Firefox → Core
Er... doesn't comment 0 explicitly say the problem is in the graphics part not the JS part? Stephen, what operations exactly is the "Just Graphics" part measuring?
Assignee: general → nobody
The graphics-only benchmark is defined here: https://github.com/concord-consortium/lab/blob/a1762680ccd636b60feae4626ca52606d2208d67/src/examples/interactives/application.js#L361-375 ... and measures the time to run the update_drawable_positions method 100 times in the MolecularContainer view here: https://github.com/concord-consortium/lab/blob/a1762680ccd636b60feae4626ca52606d2208d67/src/lab/md2d/views/molecule-container.js#L1202-1221 The work involves reading model state from arrays and objects and creating and manipulating SVG. The slowdown measured in the benchmark compared to Chrome and Safari is similar to the actual performance difference just running the model in the browser.
Thanks. Chances are, this is gated on SVG perf, but needs a profile..
Component: Graphics → SVG
profile of the benchmark : http://people.mozilla.com/~bgirard/cleopatra/#report=0496ebe52f8a97e7066701cce9f23aeb8ca11929 Profile of the demo : http://people.mozilla.com/~bgirard/cleopatra/#report=4de343b3bbf72bf1dcf2c049f23d7cc62545fe6a Ie10 preview on win7x64 is much smoother than the latest nightly20.
've just taken performance measurements from nightly versions of Firefox, Chrome, and Safari all running on the same 2010 Macbook Pro and shared the results here: https://docs.google.com/spreadsheet/ccc?key=0AtvlFoSBUC5kdEFGT2NaY2ZXWGZoN0FmOFpzT3c1OGc Looking just at column 9: model (steps/s) [which is column J in the spreadsheet) Firefox model-only performance is just a bit slower than Chrome for the first (2-oil-and-water-shake.json) and third (benchmarks/7-plasticforces.json) models -- while only 60% of the speed of Chrome on the second model: benchmarks/5-100-atoms.json. From the "About" box for benchmarks/5-100-atoms.json: This model has 100 charged atoms, this means that the modeling engine spends proportionally more time calculating pairwise forces for the long-range Coulomb forces than in some of the other models. Since there are no bonds and no display of VDW lines the view is less computationally intensive than other benchmarks. If you are interested I can show the different code paths the modeling engine takes when more of the long-range pairwise forces are included in the calculations. Looking at performance in general combine the engine and view Firefox performance ranges from 25-50% as fast as Chrome. Earlier the graphics performance of FF was much slower but in these latest tests (FF nightly AND improvements in our code) FF view performance is comparable to Chrome ... so I'm marking this issue as resolved ... But, I don't know what to make of the poor performance when running the model+graphics test or the fps test ??? See discussion continuing in this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=791699
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.