I’m evaluating the Telerik grid and at the moment the performance test is on my focus. I’m using the latest Silverlight 3 components.
This brings me to the question how the best performance strategy looks like when using the Telerik GridView. I’m really happy with the grouping and especially with the filtering functionality as activated in XAML with IsFilteringAllowed=”True” and I would be glad to use this kind of functionality also with a bigger amount of data. I know that often the answer concerning the performance will be “it depends” and may be from your experience there are different strategies necessary, but it would help me a lot if you could share your thoughts. May be one strategy is up to several thousand and a different one for ten- or hundred thousand records.
I’m played around a bit with the grid and that’s my experience until now. I’m using ADO.NET Data Services to access the db on the server. In my first test I’ve loaded a table with ~ 1.700 records (10 columns) into the grid. I’ve used the DataLoadMode=”Asynchronous” attribute. It took approx. 10 sec to load the grid. During the loading the application was more or less responsive. The problem I have is that during loading nothing seems to happen. The grid remains empty for nearly the whole 10 sec and no progress indicator was shown. My question is, if it’s somehow possible that the grid is filled asynchronous during loading so the first page is shown more or less immediately and that during the complete loading process the progress indicator is shown.
A better strategy seems to be to have data virtualization that only the data are loaded which are shown in the UI. I’ve seen there is a server page, sort and filter example which seems to be more useful when dealing with a bigger amount of data. I haven’t checked this until yet but I’ve seen the filter strategy is different.
In addition I’ve read in other posts that you are working at the moment at the performance and virtualization behavior for the grid. So can you please tell me your opinion how the best performance strategy for the grid looks like and which still supports e.g. the filter functionality. And very important to know is also which functionality comes out of the box and which one has to be created by oneself.
A very honest assessment what’s possible with the grid and what’s just wishful thinking would be greatly appreciated. If I show e.g. a customer the auto filter functionality of the grid which he knows from Excel and at the end I can’t deliver the functionality because of performance issues, then I would prefer to use a different filter strategy from the beginning to avoid disappointments at customer site.
I know I can test everything on my own or create missing functionality, but this takes more time that I have at the moment so a helping hand with this questions would be very welcome.
If I have to wait until end of August for a new version, with increased performance and virtualization functionality than it’s not a big problem for me. I would just like to know which way is probably the best way to avoid that I have to modify too much when the new version is released.
Thanks for you support