Hi, I was trying your JavaScript 64-Chart Dashboard Performance Demo and noticed few problems about it.
It shows 60Fps and chrome Fps shows only ~15fps and that is obviously lag in my eye.
Another problem was when I resized window it started to jump up and down when fps was below 10 and after above 10 it resized it continuously. Also when labels is added in small window it start jump when try to resize charts…
When I zoomed close to mountain series it changed visual data after moved that to left so there is some problems on your algorithm what you use to group that data to screen in real time.
-Astrid
- Astrid Bergqvist asked 1 year ago
- You must login to post comments
Hi
The render time at the top of the chart shows the time to draw the entire surface of 64 charts.
The data is updated every 20ms so we’re not trying to draw at 60FPS. The MaxFPS figure is calculated as min(60, 1000 / rendertime). Obviously the performance you get will depend greatly on the hardware you have and what else your computer is doing.
Resizing a window continually is making the browser do quite a bit of extra work. You wouldn’t do that if you were actually using a chart in a real application though.
I can’t see the issue with the mountain chart you mention. This is just random data. We’re more concerned with the quantity than the exact shape for this demo.
Ultimately this is really to show what SciChart can do with the new SubCharts API and native text, without even thinking much about performance optimization. This is also first release of these new features. There are lots of improvements to come.
Regards
David
- David Burleigh answered 1 year ago
- last edited 1 year ago
- You must login to post comments
Please login first to submit.
