Who Makes the Fastest ASP.NET Datagrid?

If you visit the sites of the major ASP.NET component vendors, you'll discover many claims about the richness, flexibility, ease-of-use, attractive design, and so on.

However, when it comes to a datagrid and large datasets, eye-candy isn't enough. Web developers want to know about the speed and efficiency of the control. Will it bog down under big loads?

Some vendors make bold claims about their grids.  Specifically,  Developer Express says "when exploiting the new capabilities of ASPxGridView along with our dataset providers, nothing can match the speed and memory footprint of the ASPxGridView".

Did Developer Express say "nothing" can match its product? Well, Jimmy Petrus of Intersoft Solutions is openly challenging the Developer Express speed claim. In his blog, Petrus says his "apple to apple" test shows that Intersoft's  WebGrid.NET Enterprise 6.0 is faster and uses less memory.

ComponentArt doesn't get into the hard numbers game with its grid. It just states that "ComponentArt Grid offers the lightest page footprint and fastest performance in the industry."

Likewise, Telerik makes a vague claim that "Telerik RadGrid is the fastest client-rich Datagrid for ASP.NET."

Infragistics doesn't claim to have the fastest grid. The features page for NetAdvantage WebGrid emphasizes style and richness over speed. However, it says the use of XML and XSLT "allows the WebGrid to render a nearly-unlimited number of rows without performance degradation."

As far as I can tell, ComponentOne doesn't make speed claims for its C1WebGrid component. It sticks with safer terms such as "lightweight" and "small footprint".

As a reviewer for Visual Studio Magazine, I've toyed with the idea of developing an online "ASP.NET drag race" for independent, side-by-side comparisons. Unfortunately, conducting a fair, scientific, verifiable, Consumer Reports-style review is beyond my expertise and bandwidth.

A rating review would be a huge undertaking and guaranteed to generate more heat than light because each vendor would want the tests tweaked to take advantage of their product's strong points. Do you measure real performance or perceived performance? The latter is quite subjective but very valuable to end-users. The free ASP.NET UpdatePanel increases perceived performance even when adding overhead.

I wondered whether the Component Vendor Consortium  would like to take on a speed test review of this type. However the CVC seems to have disappeared. Its URL has "gone to squatter".

9 Comments

  • What is the fastest Grid for ASP.Net?
    I wouldn't know, but there's also the Grid from Obout:
    http://www.obout.com/

    They also claim their Grid is fast. I guess it all depends on what you want to achieve, but nothing beats a regular table in speed. :p

  • If speed is a concern - Why on earth would you use a commercial Grid? Nothing beats a home grown roll your own grid using a datareader. Commercial grids have to be everything to everybody - just the amazing number of lookups that occur for properties and events that most people don't use makes them big losers when it comes to speed.

  • Jim,

    Telerik Grid is fast, because they dont take account the sorting, grouping, filtering and data aggregation part.

    Try to set a column to use Sum or Count aggregate. See if it returns the paged result, or the true total result.

    AFAIK, they will take more than 30 seconds when you tried to enable the data-operation features. You can check it for proof, for sure. :)

    Regards,
    James.

  • Why would anyone use a datagrid when all they need is a table? Maybe the whole point is that you often need much more than a table and hand coding the sorting, grouping, column resizing etc. is much more hassle and expense than finding a great datagrid that doesn't bog down under heavy load or that doesn't bloat your webpage beyond reason.

  • Jim,

    That sample only bound to a table with 77 records. Does it bound to a table with 350.000 records?

    Regards,
    James.

  • Vlad,

    It's ok, don't take it too seriously :)

    Eventhough you can make the Aggregate to work, it's still slower compared to the grids mentioned in this post. In your simple 10 rows Grid, it took around 6 seconds for sorting and paging. I guess it will take more if you have like 20-40 rows per page.

    Good luck!

    James.

  • Sorry James however you missed the fact that the grid is bound to 1mil. records :) Can you post an example where other ASP.NET grid bound to 1mil. records can sort, page or filter faster?
    I'm not sure also how records displayed per page will decrease performance of sorting or filtering with such small change (20-40 records)? Well if you try to retrieve at least 5000 records per page - that's another story :) however even in this situation the grid data-binding performance will be the same.

    Warm Regards,
    Vlad

  • While speed is a really important factor and probably the most important factor, there are numerous other things that I've looked for when evaluating a grid (or any component for that matter).

    * Feature set and API
    * Broswer compatability
    * Compatability with other components
    * Vendor support
    * Community support (usually through vendor supported forums)
    * Standards compliance (XHTML)

    Not all the grids mentioned throughout the blog post and user comments can come close to eachother when looking at these other factors. I actively use several of these products depending on the use for the grid, but have had completely different experiences with the above factors between different companies. I have gladly given up a bit of speed to make significant gains in some of these areas, particularly vendor and community support.

    -Chris

  • There's a grid lock between grid vendors on who's grid is the fastest.
    Grid vendor 1: My Grid is the fastest.
    Grid Vendor 2: My Grrr!d

    Developers realized this grid lock, dumped all 3rd party controls and simply embraced jQuery.
    They realized how easy it is to implement just the features they need...in no time...with very little effort.

    Every one lived happily ever after....

    Until...

    The vendors embraced jQuery too and started fighting on their implementations of jQuery Grid :)

Comments have been disabled for this content.