3 ms·
In regards to rendering performance, we have this internal app that's pushing a lot of points into timeline charts rendered with HighCharts. When all the datapo
by bad_user 13y ago
In regards to rendering performance, we have this internal app that's pushing a lot of points into timeline charts rendered with HighCharts. When all the datapoints are rendered, Chrome has a lot of latency but is still usable, whereas Firefox chokes. I see that in Australis it's much improved, but still less usable than Chrome.
This is awkward since in general I find Firefox's performance to be on par with Chrome, sometimes slightly better, but these charts make me open Chrome and it's a pity since I prefer Firefox.
Maybe HighCharts is not optimized properly for Firefox and of course, those charts being a work in progress are not optimized. But I do wonder, what's the difference here? Is it something about hardware acceleration?
- RussianCow 13y agoI've found Chrome's graphics performance in general to be better than Firefox's, specifically with regards to canvas and SVG. Not sure the reason, but my guess is just lack of optimization.
- AshleysBrain 13y agoChrome can make graphics calls in a separate thread, whereas I think Firefox still makes graphics calls on the main thread.
- nnethercote 13y agoInternal apps are hard for Firefox devs to debug, but I've had success in the past debugging problems in internal apps by using a test account where the developers have emailed the login details to me privately. If you are able to provide such a test account, please file a bug at https://bugzilla.mozilla.org/enter_bug.cgi; https://bugzilla.mozilla.org/enter_bug.cgi; use "Core :: General" in the "find product" box; and don't worry too much about most of the fields, the title and description are the most important; and also add ":njn" to the "CC" field. Say something like "I can provide login details privately". If you can do that, I'll try to find the right person to address it.