WPF CHARTS PERFORMANCE BENCHMARK Page 1 / 16. February 18, 2013

Transcription

1 WPF CHARTS PERFORMANCE BENCHMARK Page 1 / 16 Test setup In this benchmark test, LightningChartUltimate for WPF s performance is compared to other WPF chart controls, which are marketed as high-performance charting products. Benchmark application was developed and test performed February 2013, with newest available chart versions. The chart controls participating in the test are in random order: Arction LightningChart Ultimate for WPF v Visifire v Visiblox Ultimate v Infragistics xamdatachart, v.12.2 The benchmark is divided in two parts: - Opening large data set and rendering in the graph (Data binding) o Line o Area - Real-time monitoring as a scrolling graphs o Line o Area Computer hardware and operating system The benchmarks were run with mid-performance class desktop computer, at the date of the test. System information: - Intel i5 Quad core CPU, 3.3 GHz - 8 GB RAM, - AMD Radeon HD GB display adapter, Full HD (1920 x 1080) resolution through the test - Windows 7 64-bit OS. Benchmark application: - WPF application, target.net framework 4.0 Client Profile, compiled to Any CPU configuration, runs in 64-bit mode in this test machine.

2 WPF CHARTS PERFORMANCE BENCHMARK Page 2 / 16 Benchmark 1 Rendering large data set A data array is generated and passed to each chart and rendering delay is measured programmatically from event handler that should notify when rendering is done. Some chart components use non-synchronous updating and raise these events much before it is actually rendered, and with those, a video camera has been used (Canon Firewire DV camera, PAL, 25 frames / sec). The video is then analyzed frame-by-frame and delay is calculated (1000 ms * frame count / 25). Synchronous charts are also checked with video camera, to verify it that it really is synchronous. All charts are set to equal size, and simplest possible appearance. The fastest rendering series types from each chart component are used, component manufacturers online examples are made use of and technical support have been contacted to make it run in optimal performance and to provide equal odds for every manufacturer. The test is performed with various point counts. The data is random numbers progressing in X axis. Test will be aborted if the chart is not able to render specified data amount in 1 minute. In line test, the best and only actually correct output is a polyline, going from data point to another. Some charts failed to do this, and rendering output was totally something else than a polyline.

3 WPF CHARTS PERFORMANCE BENCHMARK Page 3 / 16 Test type Line series Series count Points/series Competitor A Competitor B Competitor C LightningChart Ultimate Rendering delay, ms LightningChart Times faster (A/B/C) (B 3 586/626/ (B /1320/ (A > (B 6 106/ / (A > (B 21 22/ / (A >60000 > / / >60000 >60000 > / / (B 3 586/653/ (B /1120/ (A > (B 8 105/ / (A >60000 > / / (A >60000 > / / >60000 >60000 > / / Area series (B 8 255/280/ (B /445/ (A >60000 > / / (A >60000 > / / >60000 >60000 > / / A) Not a polyline, but some kind of high-low area trick. B) Not a continuous polyline Rendering delay, ms /880/ /4980/ > / / >60000 > / / >60000 > / / /512/ /2302/ > / / >60000 > / / >60000 > / / /87/ /275/ >60000 > / / >60000 > / /

4 WPF CHARTS PERFORMANCE BENCHMARK Page 4 / 16 Benchmark 2 Real-time monitoring Appending of data points in a scrolling view. X Axis represents time, length is 10 seconds. Data points have fixed X step. When chart is full (X axis maximum is reached), the scrolling starts. The chart appearance is defined as fast as possible (simplest possible). The test continues until 1 minute is reached, or chart does not updated at least once per second. Feeding data with specified series count / sec, at point count /sec for each series, as waveform (progressing time data). Waveform types: - Sine - Spike data, flat 0 line, a peak value generated every second. This is used to check that the chart does not remove any details of the data (down-sample it by just observing a fraction of values). Series types in the test are: Line and Area. Refresh rate of the chart is observed, with the charts that have a synchronous updating, or accurate event that reports when the chart has been rendered on the screen, a FPS calculator is used. With non-synchronous charts, a visual interpretation is made

5 WPF CHARTS PERFORMANCE BENCHMARK Page 5 / 16 Test type Series count New points /sec/series Competitor A Competitor B Competitor C LightningChart Ultimate, Average FPS Line series Sine OK OK Not possible 100, OK Not possible Not possible 99, Not possible Not possible Not possible 100, Not possible Not possible Not possible 100, Not possible Not possible Not possible 96, Not possible Not possible Not possible 27, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 99, Not possible Not possible Not possible 98, Not possible Not possible Not possible 99, Not possible Not possible Not possible 93, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 69, Not possible Not possible Not possible 70, Not possible Not possible Not possible 43, Not possible Not possible Not possible Not possible Spikes OK OK Not possible 100, OK Not possible Not possible 99, Not possible Not possible Not possible 100, Not possible Not possible Not possible 100, Not possible Not possible Not possible 98, Not possible Not possible Not possible 77, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 99, Not possible Not possible Not possible 100, Not possible Not possible Not possible 98, Not possible Not possible Not possible 95, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 89, Not possible Not possible Not possible 92, Not possible Not possible Not possible 88, Not possible Not possible Not possible Not possible

6 WPF CHARTS PERFORMANCE BENCHMARK Page 6 / 16 Test type Series count New points /sec/series Competitor A Competitor B Competitor C LightningChart Ultimate, Average FPS Area series Sine OK OK Not possible 101, OK Not possible Not possible 100, Not possible Not possible Not possible 101, Not possible Not possible Not possible 49, Not possible Not possible Not possible 80, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 100, Not possible Not possible Not possible 61, Not possible Not possible Not possible 28, Not possible Not possible Not possible 4, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 16, Not possible Not possible Not possible 6, Not possible Not possible Not possible 4, Not possible Not possible Not possible Not possible Spikes OK OK Not possible 102, OK Not possible Not possible 102, Not possible Not possible Not possible 101, Not possible Not possible Not possible 49, Not possible Not possible Not possible 64, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 100, Not possible Not possible Not possible 59, Not possible Not possible Not possible 27, Not possible Not possible Not possible 45, Not possible Not possible Not possible Not possible Not possible Not possible Not possible 18, Not possible Not possible Not possible 7, Not possible Not possible Not possible 5, Not possible Not possible Not possible Not possible

7 WPF CHARTS PERFORMANCE BENCHMARK Page 7 / 16 Conclusion In the world of WPF, it is a common delusion to assume that WPF rendering routines would make graphics render fast. The benchmark results here indicate, that they are not practically any faster than GDI+ rendered WinForms chart controls. Rendering of 100,000 in a WPF chart can take longer than 1,000,000 points in a GDI+ chart (refer to Benchmark of LightningChart Pro/Ultimate for WinForms vs. other WinForms charts, in 2010). Many WPF chart manufacturers that advertise their charts as a high-performance products, can be set under a big question mark based on their real performance. Some manufacturers also try to trick with techniques that don t produce correct rendering output, such as down-sampling and high-low fill rendering. Even if WPF rendering is distantly based on DirectX, it falls way behind of real DirectX rendering in performance aspects. LightningChart Ultimate for WPF uses low-level DirectX rendering, not WPF s graphics routines. And it really stands out of the competitors, let it be real-time monitoring or rendering a large data set. Eventually the difference is like setting a dragster with bunch of bicycles into quarter-mile drag race. Rendering large data set, Line series rendering of 10,000 data points LightningChart is times faster than competitors, while Competitor C renders it wrong. Shorter bar is better

8 WPF CHARTS PERFORMANCE BENCHMARK Page 8 / 16 Rendering large data set, line series rendering of 1,000,000 data points LightningChart is times faster than competitors, while competitor A cheats with highlow fill rendering, and competitor B is unable to render it, and competitor C renders it wrong. Shorter bar is better Rendering large data set, Area series rendering of 10,000 data points LightningChart is times faster than competitors. Shorter bar is better

9 WPF CHARTS PERFORMANCE BENCHMARK Page 9 / 16 Real-time monitoring, Line series, appending of capacity of new data points / sec, 1 series LightningChart Ultimate: 10,000,000 Competitor A: 1,000 Competitor B: 100 Competitor C: - LightningChart is times faster, while Competitor C couldn t provide any result. Longer bar is better Real-time monitoring, Line series, appending of capacity of new data points / sec, 40 series LightningChart Ultimate: 100,000 Competitor A: - Competitor B: - Competitor C: - LightningChart is the only one that could provide result with 40 series, and also with that, provides 1000 times better capacity than Competor B with only 1 series.

10 WPF CHARTS PERFORMANCE BENCHMARK Page 10 / 16 Power-to-cost ratio This is completely beyond of the test, but it s interesting to compare power-to-cost ratio, in the similar way than with sports cars. The list prices with priority support included: o LightningChart Ultimate: USD 2,470.00, comes with both WPF and WinForms chart and other controls o Competitor A: USD 2,395.00, comes with a lot of other components o Competitor B: USD 1, o Competitor C: USD Max point count in line series, that gets rendered before 2 seconds. LightningChart: 100,000,000 points in 1813 ms Competitor A: 1,000,000 points in 480 ms Competitor B: 1,000 points in 1880 ms Competitor C: 100,000 points in 840 ms Longer bar is better LightningChart is slightly the most expensive, but provides unmatched power-to-cost ratio.

11 WPF CHARTS PERFORMANCE BENCHMARK Page 11 / 16 Some screenshots during the testing, a couple of problems noted too LightningChart, Real-time 4 series, sine waveform, 100,000 new points /sec/series.

12 WPF CHARTS PERFORMANCE BENCHMARK Page 12 / 16 Competitor A, rendering large data set, random waveform, areas, 4 series, 10,000 data points/series LightningChart, Real-time 40 series, sine waveform, 100,000 new points/sec / series.

13 WPF CHARTS PERFORMANCE BENCHMARK Page 13 / 16 LightningChart, Real-time 4 series, spike waveform, 1,000,000 new points/sec / series. LightningChart, Rendering large data set, random waveform, 40 series, 1,000,000 data points/series

14 WPF CHARTS PERFORMANCE BENCHMARK Page 14 / 16 Competitor A, rendering large dataset, 4 series, 1000 points /series. Rendering OK. Competitor A, rendering large dataset, 4 series, 10,000 points /series. Not a polyline, but High-low fill trick instead.

15 WPF CHARTS PERFORMANCE BENCHMARK Page 15 / 16 LightningChart Ultimate, correct polyline rendering, with random data + spikes every second.

16 WPF CHARTS PERFORMANCE BENCHMARK Page 16 / 16 Competitor C polyline rendering problems. Pixels missing in line segment joints.