Webgrid 7.0 with operating on larger datset performance tune

vinsdeon — Thu, 08 Oct 2009 08:19:35 GMT

Concider the following scenario:

1. The datasource is assigned through initialiselayout by assigning datatable retrieved through sql proc.

2. The table consists of min 15000- max 60000 records.

3. Most of the operations like sorting, grouping on webgrid has to be performed.

4. Display requirement is 100 records(or 75 records) at a time.

5. Client binding or normal one could be used(However am unable to do client binding for webgrids with larger data).

6. Client binding means i cant use initialise row(if am correct). Am hiding some columns and makes it available to client side through adding it as attribute through initialise row. So i wonder if any alternative is possible in that case.

7. Is there a way by which i can make the javascript combined, and only those which are absolutely necessary for a page.

8. And for paging, what are the ways to do it effectively. I mean to get 100 records at a time and go to server for fetching next 100 records would be the efficient way than to feth 60000 records at a time.

Now with current compression enabled strategy(through web.config) and caching javscript and css and other static images, my page with 15500 records takes 8 to 10 secs on local server and around 20 secs in server. Concidering am having 2mbps broadband connection with a min 100kbps speed the delay is huge. So would like to know what are the optimisations could be done for webgrids with large amount of data? Please clarify my post

Intersoft Community - WebGrid Enterprise - Webgrid 7.0 with operating on larger datset performance tune

Webgrid 7.0 with operating on larger datset performance tune