How to improve dashboard performance and decrease loading time

Martin Brekhof

created 12 years ago (modified 11 years ago)

Hi,
I did some experimenting with the Dashboard component using the online docs and my own (SQL Server 2008) database. Based on my experience I have some questions:

The component just stops with an out of memory error when querying a 700.000 records tables during the initial load determining the fields. why do not something like a 'top 1' , 'where 1=0' or whatever modification so the fields list can be retrieved in sub-second times?
If the problem mentioned at 1) gets solved will we then run into the problem that the query times out when retrieving the data for manipulation in (e.g.) a pivotgrid? If so, what/who is the intended audience of this functionality (taking the number of records it can handle as a measure)?
regards
Martin

Answers approved by DevExpress Support

DevExpress Support Team

created 12 years ago (modified 12 years ago)

Hi, Martin
Thank you for your question. The appearance of a dashboard depends on its underlying data, so the Dashboard Designer should load all the data from the data source. That's why we do not use Top or Where clauses in the Designer. You can do this yourself by writing a custom SQL query in the Data Source Designer (for example, use top 10000), but this will affect content of the dashboard.
Also, the current version of the Dashboard does all calculations on the client side. It loads all data in memory to process it.
So, to make calculations take a reasonable time, you need to significantly reduce the number of loaded rows. At this moment, you can do this in the following ways:

Reduce a datetime range for data, for example, create a view that will select last several months, weeks or days, depending on your data.
Aggregate your data to larger pieces - for example, in the AdventureWors database, you can group sales by weeks.
Create an external filter control (like a list box or a range filter) for a dashboard and load data programmatically using its selection. See the Change data in Dashboard issue for more details.
I have also duplicated this issue to the Data Binding - Provide the server-side data processing mode (Server Mode) suggestion. You will receive a notification when the server mode is implemented. This mode should resolve problems caused by loading a huge amount of data…

Show previous comments (4)

Martin Brekhof 12 years ago

Ok, I was hoping for some 'async' stuff or a way to enable server-mode. I'll go with the SQL views option for now. Thanks.

Henry Ong 12 years ago

When do you all plan to implement server side loading. It is not practical for real life application if we have to limit data in this manner.

Jascha 12 years ago

+1. A form of (XPO?) server mode that allows pivots, reports and dashboards to retrieve data summarised to the necessary level would be great if that were possible. Otherwise any analysis that does client side processing (via XPO or SQL) is highly likely to fail for larger data sets.

Mark Couvaras 12 years ago

I agree this needs to be done, keep getting out of memory exceptions when binding to a large dataset

DevExpress Support Team 12 years ago

This issue is duplicated to the Data Binding - Provide the server-side data processing mode (Server Mode) suggestion. You will receive a notification when the server mode is implemented. This mode should resolve problems caused by loading a huge amount of data.

Mike_Grace 11 years ago

me too.

Gustavo Marzioni 11 years ago

I agree with Martin, even the top n feature (or async mode) would be great for design mode, where all editing tasks are very, very slow with large datasets

How to improve dashboard performance and decrease loading time

Answers approved by DevExpress Support

Recently viewed tickets