3 ms·

I am for all intents and purposes a massive Mozilla fanboy, however I regularly switch to Chromium to use any nontrivial 2D graphics js (e.g. the Python plop pr

I am for all intents and purposes a massive Mozilla fanboy, however I regularly switch to Chromium to use any nontrivial 2D graphics js (e.g. the Python plop profiler). Not sure why, but Firefox definitely seems to have a weak spot around 2d (SVG?) performance

bloodorange 13y ago
I submitted three (minor) patches for improving the performance of a couple of filters in Mozilla's SVG code. Those (minor) optimisations should be in this release. I hope to do a lot more. I too, like you, am a Mozilla fanboy. Unfortunately, in the last few months, I have a lot of pressure at my day-job (a few sudden departures). Nevertheless, I did contribute when I could spare the time and I urge you to do likewise. If there are enough of us, then there's always someone helping them out. It's a massive project and needs all the hands that kind developers are willing to spare.
- vidarh 13y ago
  If you (or anyone else with time...) want to be a true hero, figure out why font changes for text on canvas is a magnitude or more slower on Firefox than Chrome. At least on the versions I've tested... I have an app that places a few hundred text labels on a canvas, and on Chrome I can do that smoothly in a single callback. For firefox I had to use a hack with a queue that is processed a few items at a time with setTimeout() to prevent it from stalling the UI for many seconds... Even so, the experience is still worse on Firefox.
  - bzbarsky 13y ago
    I'm happy to link into this if you point me to a testcase that shows the slowness. If it takes a few tens of seconds so much the better: easier to profile.
    - bzbarsky 13y ago
      I meant _look_ into this, of course...
jwatt 13y ago
There have been many large performance improvements to the SVG implementation over the last few months. Check out the latest http://nightly.mozilla.org/ http://nightly.mozilla.org/ and if you still see issues then please do file SVG bug reports at https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp... and I'll take a look.

bloodorange 13y ago

I submitted three (minor) patches for improving the performance of a couple of filters in Mozilla's SVG code. Those (minor) optimisations should be in this release. I hope to do a lot more. I too, like you, am a Mozilla fanboy. Unfortunately, in the last few months, I have a lot of pressure at my day-job (a few sudden departures). Nevertheless, I did contribute when I could spare the time and I urge you to do likewise. If there are enough of us, then there's always someone helping them out. It's a massive project and needs all the hands that kind developers are willing to spare.

vidarh 13y ago
If you (or anyone else with time...) want to be a true hero, figure out why font changes for text on canvas is a magnitude or more slower on Firefox than Chrome. At least on the versions I've tested... I have an app that places a few hundred text labels on a canvas, and on Chrome I can do that smoothly in a single callback. For firefox I had to use a hack with a queue that is processed a few items at a time with setTimeout() to prevent it from stalling the UI for many seconds... Even so, the experience is still worse on Firefox.
- bzbarsky 13y ago
  I'm happy to link into this if you point me to a testcase that shows the slowness. If it takes a few tens of seconds so much the better: easier to profile.
  - bzbarsky 13y ago
    I meant _look_ into this, of course...

jwatt 13y ago

There have been many large performance improvements to the SVG implementation over the last few months. Check out the latest http://nightly.mozilla.org/ http://nightly.mozilla.org/ and if you still see issues then please do file SVG bug reports at https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp... and I'll take a look.