Performance Comparison Across Versions
We used Microsoft's Contoso Database to measure PivotGrid performance and compare numbers for different versions. The test query returns 3.4M records. We requested values from ProductName, ProductSubcategoryName, ProductCategoryName, DateKey dimensions, SalesAmount, and SalesQuantity measures. In the pivot grid, we display both measures and group data by ProductName, ProductSubcategoryName, ProductCategoryName dimension values and Year, Quarter, and Month values calculated by the DateKey dimension.
Changes in v19.1
The LegacyOptimized data processing engine supports all pivot grid features including the Running Totals feature.
Changes in v18.2
Starting with this version, the new LegacyOptimized data processing engine supports all pivot grid features except the Running Totals one. The LegacyOptimized engine is enabled out-of-the-box. However, you can switch back to the old engine by setting the DataProcessingEngine property to the Legacy value.
We expect that in most cases your projects should run correctly without any modification. If you face any problem, please refer to the T683512: What is the difference between the Legacy and Optimized data processing engines article to determine the cause of this issue.
Changes in v18.1
We continue to improve the Pivot Grid's in-memory data processing. The following features are now processed by the pivot grid in Optimized Mode:
- Unbound Expressions
Changes in v17.2
Starting with v17.2, Pivot Grid's LegacyOptimized data processing mode can leverage performance benefits offered by multi-core processors. The control splits bound records into separate bulks and processes them in parallel threads. This means you can expect performance improvements proportional to the number of CPU cores.
A few limitations to the LegacyOptimized mode still remain in v17.2 including unbound expressions, top N records and running totals. We plan to address these issues in v18.1.
Changes in v17.1
Our R&D team begins a data processing engine overhaul, which is estimated to boost performance up to 30 times compared to v16.2.
While working on new data engine support, we managed to enable faster data processing for certain operation types in the upcoming v17.1 release. These enhancements are estimated to boost performance up to 3-7 times compared to v16.2. We would appreciate if you install the current v17.1 Beta version, upgrade your applications using the Project Converter and let us know how the new mode works. The new data processing mode is automatically enabled in WinForms, ASP.NET and WPF PivotGrid Controls.
Please remember that the following data processing tasks have not yet been optimized in v17.1:
- Calculation customization: Unbound Expressions, Custom Summary, Custom Group Intervals, Custom Unbound Data, Custom Sort
- Binding to custom objects
- Top N option, Running Total, Summary Filter, DrillDown operations
When we officially launch v17.1 we plan to make the new mode optional. To turn it on, you would need to set the OptionsData.DataProcessingEngine option to LegacyOptimized.
Show all comments