SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, iOS Chart, Android Chart and JavaScript Chart Components

Answered
0
0
  1. Open Firefox.
  2. Go to scicharts demos, for example https://demo.scichart.com/javascript-multi-pane-stock-charts

Rendering speed is much slower than in Google Chrome; scrolling is freezing.
Also there are several errors and warnings in console.

Version
2.0.2179
Images
  • You must to post comments
Best Answer
1
0

Hi Sergey,

It is a known issue that rendering WebGL in Firefox is slower than in Chrome – https://stackoverflow.com/questions/62836595/webgl-performance-differences-between-firefox-and-chrome , also I created a task to investigate it regarding scichart.js https://abtsoftware.myjetbrains.com/youtrack/issue/SCJS-977

I can confirm we have some errors/warning in firefox, I created a task to sort it out https://abtsoftware.myjetbrains.com/youtrack/issue/SCJS-976 , but as far as I can see those errors/warnings are not critical and they do not break the app.

Best regards,
Michael Klishevich

  • You must to post comments
Best Answer
0
0

Actually it’s not the WebGL rendering alone in Firefox but also the rendering to final HTML5 canvas which is extremely slow.

There are several open bugs here reported for Firefox canvas performance reported on Bugzilla:

There’s not a great deal we can do here. We have to draw the image to canvas. We can internally improve our performance as much as we like but if the browser implementation of key functions is poor then we’re stuck.

Talking of SciChart performance, we do have a build we are working on now that will massively improve rendering performance & text drawing performance but still will be subject to the same limitations as above. It will still perform better in Google chrome, which just has a superior implementation of key functions.

Best regards,
Andrew

  • You must to post comments
Best Answer
0
0

Update. I’ve commented on some of those Mozilla bugs above and we’re looking into any possible solutions on our side. They may take some time, working around a core function in a browser is a challenge.

Thanks for reporting!
-Andrew

  • Sergey Chernyakov
    Hello, Andrew. Thank you for your detailed response. I am looking forward with optimism.
  • Andrew Burnett-Thompson
    Thanks Sergey. We have some potential solutions. One thing you can do. Use SciChartSurface.createSingle() not SciChartSurface.create(). This uses one WebGL context per SciChartSurface. Firefox allows up to 300 WebGL contexts but Chrome, Edge, Safari are limited to 16. The SciChartSurface.create() API uses a single shared WebGL context which adds overhead to Firefox. Regarding the solutions on our side: we have a way to draw text which reduces load on FF. Will be releasing that later in January.
  • Sergey Chernyakov
    Hello Andrew. Thanks for explanation and suggestion. I have tried it on candlestick series with volume on 3000+ values. It is not perfect, to be honest , but performance is much better than using SciChartSurface.create. Can you please clarify: WebGL context is limited per tab, per host or per bowser instance?
  • Andrew Burnett-Thompson
    Good question. I believe it’s per browser process and the WebGL context limit is much lower for chrome, safari, edge. Mobile browsers even lower (8 contexts). Firefox is the outlier here with 300 contexts. We are working on some performance improvements here including (1) text rendering – a bottleneck in Firefox (2) series drawing. If for now you detect which browser and use SciChartSurface.createSingle() for Firefox, and create() for all others you will see a performance improvement
  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.