3 ms·

I've found the gap in rendering performance between chrome and firefox to be enormous (in a number of areas) - didn't realize this until I started doing some pr

by math 11y ago

I've found the gap in rendering performance between chrome and firefox to be enormous (in a number of areas) - didn't realize this until I started doing some pretty intensive visualization stuff lately. are those numbers you cite just javascript benchmarks?

codemac 11y ago
Yes - it's focused on their javascript engine. As far as visualization stuff, are you on linux? I found out that firefox by default turns off the off main thread compositing support. Enabling this was a huge performance boost for me, it's really bizarre they don't enable it. If you're not on linux.. I'd be curious what performance issues you're having on Firefox.
- math 11y ago
  on a mac. SVG for sure, eg: http://mbostock.github.io/d3/talk/20111116/bundle.html http://mbostock.github.io/d3/talk/20111116/bundle.html I'm pretty sure other things as well including text and updating text in a text input element, though I haven't debugged the performance issues fully yet.
  - codemac 11y ago
    Hm. Well, that renders instantly for me on intel hd 5000 + firefox 41.. compared to chrome on linux and it was identical to my eyes, but I haven't measured yet.
    - math 11y ago
      On that page I was basing my opinion on woeful animation speed, but now I think that's probably some issue with events. Ok, here's what I'm working on: http://www.datavstime.com/horizons http://www.datavstime.com/horizons - i think the following are all much slower in firefox: [1] axis rendering (svg) [2] updating the date/time text in the text input elements (currently causing worse horizontal scrolling performance) [3] the value overlays (text in divs), which don't update as quickly when there are lots (say > 100) of them. The bulk of the page is WebGL which is fast in firefox (that said, I currently have a flickering problem). Note: I have plans to work around all this, but just haven't implemented it yet...

by math 11y ago

codemac 11y ago

Yes - it's focused on their javascript engine. As far as visualization stuff, are you on linux? I found out that firefox by default turns off the off main thread compositing support. Enabling this was a huge performance boost for me, it's really bizarre they don't enable it. If you're not on linux.. I'd be curious what performance issues you're having on Firefox.

math 11y ago
on a mac. SVG for sure, eg: http://mbostock.github.io/d3/talk/20111116/bundle.html http://mbostock.github.io/d3/talk/20111116/bundle.html I'm pretty sure other things as well including text and updating text in a text input element, though I haven't debugged the performance issues fully yet.
- codemac 11y ago
  Hm. Well, that renders instantly for me on intel hd 5000 + firefox 41.. compared to chrome on linux and it was identical to my eyes, but I haven't measured yet.
  - math 11y ago
    On that page I was basing my opinion on woeful animation speed, but now I think that's probably some issue with events. Ok, here's what I'm working on: http://www.datavstime.com/horizons http://www.datavstime.com/horizons - i think the following are all much slower in firefox: [1] axis rendering (svg) [2] updating the date/time text in the text input elements (currently causing worse horizontal scrolling performance) [3] the value overlays (text in divs), which don't update as quickly when there are lots (say > 100) of them. The bulk of the page is WebGL which is fast in firefox (that said, I currently have a flickering problem). Note: I have plans to work around all this, but just haven't implemented it yet...