{"id":1838,"date":"2016-05-22T15:11:50","date_gmt":"2016-05-22T14:11:50","guid":{"rendered":"https:\/\/www.scichart.com\/2016\/05\/22\/extreme-performance-optimization-survey\/"},"modified":"2022-12-09T13:09:19","modified_gmt":"2022-12-09T13:09:19","slug":"extreme-performance-optimization-survey","status":"publish","type":"post","link":"https:\/\/www.scichart.com\/extreme-performance-optimization-survey\/","title":{"rendered":"Extreme Performance Optimization Survey"},"content":{"rendered":"
From time to time at SciChart HQ, we get asked for even more performance<\/em>. Yes! I know it’s crazy,\u00a0SciChart can easily handle 10 million points<\/a>\u00a0in real-time (or even up to 100 Million points at 2-4 FPS) in a line-chart, but sometimes we get asked ‘well, can you do more?’<\/p>\n So … wait … you want more<\/span>\u00a0than 10s of millions of points? … Ok then! ..\u00a0<\/em><\/p>\n So we had a go to try to optimize certain critical paths of SciChart’s WPF Chart. Right now, we’re already using unsafe code<\/a> (pointer arithmetic in .NET) for our performance critical algorithms, plus DirectX for drawing<\/a>, however there is the potential to move certain critical routines over to C++ with SSE (Streaming SIMD Extensions<\/a>), which allow us\u00a0to vectorize and hence accelerate certain numerical methods.<\/p>\n