asp.net - GridView + ObjectDataSource issue - equally bad performance for large and small result sets -
I was called to work on the old NET Legacy Web App. The performance was quite sub-crossed lately, because the amount of data in the system was quadruple. It was fine for the past 2 years.
This can talk to an archived procedure using an .xsd file that compresses the results adequately (though no paging) and feeds them in the gridview through the Object data source . / P>
The part can not be found around my head , was it taking approximately 7 seconds to load for 1 result, 140 or 1200 . For the results of the result, the second took a split second (to mark on the GridView page)
Using the SQL Profiler, we were able to see that the query takes 6.9 seconds. Runing the same query with the same parameter, taking 100 mms in SQL Management Studio, I have changed the parameters to make sure that it is not only a cached result, while the long wait time is reliable to be reproducible.
I know it must be done here, but for now I have only been trying to find an explanation for the last time why the page is performing equally
(Gridview's 'simple' performance is fine for their needs - there is no need to control HTML)
We have the same problem:
- Check if your statistics are up to date:
DBCC Drapliquin buffers DBCC FreePrechchai
- ">
- If no one does help , You can try implementing an SSMS query plan with signals such as "joining the internal LOOP" and "with (index = ...)".
Comments
Post a Comment