Jun 23 |
Posted by Yaroslav Pelyukh on 23 June 2016 04:12 PM
|
iOS Chart Performance: TLDRIn this post, we compare the performance of three well-known iOS Charting Libraries including our own brand new & upcoming iOS Chart: SciChart for iOS. In order to conduct a fair comparison, we have developed a comparison application which generates several different chart types and measures refresh rate (FPS – Frames per Second), as well as CPU Usage and startup time on each iOS Chart library. Our findings were:
At smaller datasets all the charts appeared fine, however once we increased the volume of data and rate of updating the iOS Chart control, all of the above slowed down significantly except for SciChart iOS. In all tests SciChart for iOS registered between 2-3x faster than the nearest competitor, and in one, a staggering 30x faster. How to we measure iOS Chart Performance?iOS Chart Performance is really important to us at SciChart. We strive to have the best, and the fastest Charting controls in the world, but how do we demonstrate what we’ve achieved vs. our competitors to would-be customers? We have developed a comparison application which generates several different chart types and measures refresh rate (FPS – Frames per Second) for several different iOS Chart Libraries. We also included such numbers like CPU usage and Start time. This is then used to draw conclusions about the performance of various iOS Chart Libraries vs. our own iOS Charts. We’ve created an application which measures our Chart Performance in a number of scenarios, such as line, scatter, scrolling-line and many-series scenarios. The tests are designed to really stress the chart control and find it’s limits. There there are several factors which influence overall performance of a iOS Chart Control. Such as:
These are reflected in the test cases and show stress on different areas of the renderer. Who did We Compare Against?We have compared the performance of iOS Charts by SciChart against the some popular and renowned iOS charting libraries, including:
We also had a look at
However due to time constraints, plus poor stability and performance of these libraries when large data was appended, we have omitted them from the results – for now. The Test SetupWhat Tests are RunA number of tests are run in our iOS Chart Performance Comparison app which stress different areas of the renderer. These tests are designed to really stress the chart, by having huge numbers of series, or points, or many updates per second. A certain test is run, and FPS, or refresh rate, is measured via the CADisplayLink , which fires once after each drawing pass completes. Test Setup HardwareFor the Test Setup we have used iPhone 5s The test cases are as follows: Test 1: NxM Series Test
FPS is measured using the time elapsed between subsequentSciChartSurface.Rendered events. Areas Stressed: – Iterating Data Series – Coordinate Transformation – Drawing.
Test 2: Scatter Series Test
N Scatter points are appended to a XyDataSeries, then the chart redraws. Immediately after, the points are updated in a Brownian motion fashion and the chart is drawn again. The FPS is measured using the time elapsed between subsequent SciChartSurface.Rendered events. Areas Stressed: – Coordinate Transformation – Geometry Generation (Ellipse) – Drawing.
Test 3: FIFO Series Test
N points are appended to a FIFO (circular buffer) series, then a single point is appended (and one dropped), which triggers a redraw of the chart. The FPS is measured using the time elapsed between subsequent SciChartSurface.Rendered events. Areas Stressed: – Copying Circular Buffers (FIFO Series) – Resampling – Drawing.
Test 4: Append Data Test
Areas stressed: – Appending Data – Resampling – Auto-Ranging – Drawing.
The Test ResultsWe’ve included the test results below:
In Table FormYou can find the test results of our iOS Chart Performance Comparison below. All test result numbers are in FPS (Frames per second – Higher is Better), meaning, the average number of redraws per second during the test, as measured by CADisplayLink . We have also included start time and CPU usage – Smaller is Better for both. If a number is missed (blank), it means that a chart failed to run (crash) under a particular test-case. Test Results in Chart FormWhat iOS charting performance comparison would be complete without the results in chart form? You can find the test results plotted below: Append Points Test ResultsSciChart iOS is blue, results are FPS (Refresh rate) so higher is better. Fifo Scrolling Test ResultsSciChart iOS is blue, results are FPS (Refresh rate) so higher is better. Scatter Series Test ResultsSciChart iOS is blue, results are FPS (Refresh rate) so higher is better. NxM Series Test ResultsSciChart iOS is blue, results are FPS (Refresh rate) so higher is better. Performance Comparison ConclusionsAccording to the Performance Comparison Results, Most iOS Chart libraries are unsuitable for real-time updates on the chart. Most perform poorly once the amount of data reaches a few thousand points. By contrast, the iOS Charts by SciChart are extremely fast and show robust performance across a number of test cases including scatter charts, scrolling line series, appending line series and multiple series. SciChart should be considered a very strong contender when evaluating real-time iOS Charting Libraries for use in iOS Apps. A version of the test-application is available on request, if you would like to contact us. For legal reasons we can’t publish the names of Competitor A, but if you believe you are that competitor and wish to verify the results or submit a modification to optimize your code, please feel free. Information about second competitor – “Charts” – you can find here. Finally let us know what you think in the comments! If there’s anything else you want us to test, please ask! Best regards, The post How Fast is SciChart’s iOS Chart? appeared first on WPF Charts, iOS and Android Charts | SciChart. | |