Greetings – We are using SciChartJS in our financial application running under Openfin framework.
I would like to inquire if SciChart provides any recommended machine specifications for running such applications on its platform, specifically regarding CPU, core count, GPU, RAM, and other relevant factors.
Additionally, we are interested in understanding any potential performance impacts on SciChart if the machine lacks a GPU.
Best Regards,
Sachin Patel.
- sachin patel asked 1 month ago
- last edited 1 month ago
- You must login to post comments
Hi Sachin,
We have some browser specification information here. This doesn’t mention hardware requirements, however it does specify what minimum browsers are supported by SciChart.js
WebAssembly support
- IE Edge v16 or later
- Firefox v52 or later
- Chrome v57 or later
- Safari v11 or later
- Opera v44 or later
WebGL Support
Ideally a browser which supports WebGL2, however WebGL1 is still supported. All the minimum spec WebAssembly browsers support WebGL.
Recommended Hardware
SciChart is pretty memory, CPU and GPU efficient, and will run well on almost any hardware. We do recommend dedicated graphics (nVidia or Radeon) over integrated graphics. There are some problems for example with Intel Integrated Graphics drivers which frequently have bugs. If these occur, updating to the latest Intel Graphics Drivers often resolves the problems.
A reasonable spec PC will give you very good results with SciChart, for example 16GB of RAM, 4-core processor, dedicated graphics from the nVidia 1xxx 2xxx 3xxx series. You won’t see enormous performance gains by having the best possible GPU, as SciChart is quite balanced across CPU/GPU usage and uses both to achieve it’s results. A good solid CPU with fast memory and a mid-level GPU will give you more ‘bang for buck’ than buying the most expensive GPU.
Browser specific performance
Google chrome is by far the fastest and most optimal browser. We have seen some performance issues with Mozilla Firefox, where canvas.drawImage (something we rely on) is a bottleneck. This can be alleviated by using the SubCharts API (sharing WebGL canvas across many charts), or by following our performance tips documentation.
If you have a hardware specification you’re looking at, and would like further comment, please ask
Thanks!
Andrew
- Andrew Burnett-Thompson answered 1 month ago
- You must login to post comments
Please login first to submit.