I have an object stroke which will return a large collection (up to 200,000 records) which is bound and paged in the gridview. I am using default paging and caching on objectdatasource. Returned data is only updated weekly, so stale data is not an issue. Paging in this solution was faster than when I created a solution using custom paging.
My questions are: Is caching this record acceptable to you? If not, then why? Is any functionality counter used to see the effect on the memory that creates your cached data?
Thank you!
To answer your questions:
1) Yes a large data set Caching is okay Creating partial data set and caching it. Since then it has very static data which makes it a good candidate.
2) For such display counters, depending on the caching mechanism you use. For example, if the caching block of your enterprise library is used then the counter is created in it. See common memory counters, work sets, private bytes, etc. for common counters ...
Comments
Post a Comment