I have a dataset that contains about 7 9 columns in each record, I would like to use objectdatasource and caching. I'm sure the data do not change. But there will be a lot of users accessing the data. My question is whether it would be a good idea to cache data with 500 records. Is it optimal or not? I think objectdatasource caches per user data. So I'm wondering if there are problems with display of this size data if I cache the data.
Thank you, Sridhar.
The answer really depends on the size of the record, not just the number of them in any event, ASP.net's caching algorithm uses some recently used (LRU) algorithm which recently extracted items not used to make room for additional items. So, unless your site is either too busy or your results are too large, you should be ok to cache the result set and keep the ASP.NET cache with the most used data in the cache And should handle the details of the data used to minimize the amount used.
You may also consider using page level output caching if there is nothing user-specific on the page because it will give you slightly more performance for at least additional memory usage. To check other area controls, SQL dependencies and if the data is read-only, make sure that you are disabling the viewsto on the controls used for displaying the data.
Comments
Post a Comment