Hi,
I've noticed one issue when using a WebDataGrid that contains a large amount of data (say 19,000 rows or above) and utilizing paging (say 100 rows per page).
Unresponsive Script Message is shown when binding more than 18,000 records in FireFox.
In Google Chrome script error is happening when binding with more than 24,000 records. You can see the error in console mode of the browser.
In IE,all data will bind but its takes too much time.
After this Unresponsive script error, we cannot filter and cannot navigate to another page. "Server Not Responding" error popup from the WebDataGrid control (there are other variations of that error that I sometimes get as well).
Is there simply a limitation on how much data a WebDataGrid can manage ?
Here am attaching the solution which I used.
There is a correction in the comment posted above.
The issue was with WebHierarchicalDataGrid. I mentioned WebDataGrid instead of WebHierarchicalDataGrid.
Hello Lithin,
Thank you for contacting us and for the provided sample!
I have tested the sample with Chrome and Firefox, and everything is working fine. The only thing that I've noticed is that sometimes is taking around 6-7 seconds to load the new page or filter the data.
The tests that I've performed:
- select different page
- select last or first page
- filter some of the columns.
In general I would suggest increase the timeout period of the grid like this:
$find("WebDataGrid1")._callbackManager.setTimeout(60000); Please check this post for more information:
http://news.infragistics.com/forums/p/25369/92985.aspx#92985
Looking forward to your reply.
Hello Zdravko Kolev ,
Thanks for your responds.
can you please test with 50000 records in that solution in Firefox.
It was set to 19766 in that solution. Use 50000 instead of 19766 .
When you test with 50000 records, "unresponsive script error" alert will show on page load.
If you click on OK button,complete data will bind.
But after that "unresponsive error message", we cannot select last or first page and filter some of the columns.
"Server does not respond" error is happening.
Can you please check. Looking forward to your reply.
I've changed the select statement to request 50 000 records and the error was thrown.
I've noticed that you are using the callbackManager, although I don't know why but it was defined twice. After modifying the initializeGrid function the error no longer occur.
Code snippet:
function intializeGrid(sender, args) { $find("<%= WebDataGrid1.ClientID%>")._callbackManager.setTimeout(60000);}