RadGridView binding is slow for IQueryable

3 posts, 0 answers
  1. Datafyer
    Datafyer avatar
    66 posts
    Member since:
    Jun 2008

    Posted 03 Oct 2014 Link to this post

    I have a RadGridView which is bound to an IQueryable. The initial data load is a bit slow, but is expected. However when I scroll at all it seems the data source is queried again. Thus performing any operations against the grid is fairly slow. I have solved this a bit by implementing the data pager. I have noticed that with a data page of 50 then scrolling to the bottom of the page yields a re-query. Then scrolling to the top does the same. However scrolling back to the bottom the data is cached. After this the single page can be scrolled very quickly.

    Is it possible for the Grid to download 2 or 3 times more data than displayed, or the entire page size of content, so that it can act as a display buffer? Thus I can work with larger page sizes?
  2. Datafyer
    Datafyer avatar
    66 posts
    Member since:
    Jun 2008

    Posted 03 Oct 2014 in reply to Datafyer Link to this post

    One other observation is resizing the window requires a larger viewport and thus the grid is querying again. Thus it is only getting what can be displayed at that moment.
  3. Dimitrina
    Dimitrina avatar
    3769 posts

    Posted 06 Oct 2014 Link to this post


    Generally, the more visual elements are to be displayed, the slower the loading will be. This explains why loading in a larger window will take more time. In order to improve the performance of RadGridView, I can suggest you going through our online documentation on possible reasons why there would be degraded performance with it. 

    When using RadDataPager, then if the PageSize is 50, then 50 items should be downloaded. I am not sure on your exact implementation though. In order to avoid any misunderstanding, would it be possible for you to isolate the the issue in a demo project and send it to us? You can open a support ticket and attach the solution there.

    That way we can check it locally and we will be able to advise further. You can take a look at this blog post for a reference on how to isolate an issue. 

    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
Back to Top