I am sure this question has been posted many times, but have not got time to wade through. Apologies in advance!
I am working on a new web application which has extremely high volumes of traffic, the application uses two large(ish) data tables (approx 15,000 rows/records each - both fairly 'wide' tables....) which are each the result of various JOINS and other intensive operations.
The post query operations are unavoidable and the data structure has been optimised wherever possible.
I am debating on using the Cache and CacheDependancy classes to store these tables, but fear the 'eviction' process due to the demand in traffic and server resources generally.
I can certainly afford to build these tables once, on the first request (near Application Start), but should memory become scarce, do not want the cached data to be recreated during the application lifecycle and have concerns about how ASP.NET will manage demands on this data in such a crisis.
For example, if during a period of time, available memory is at an all time low, I would anticipate that the CacheDependancy would keep recreating the tables for each request. (I don't know...)
Note: The Cache API is not used elsewhere and the Application and Session scopes are hardly used.
At present, I am using just a static class to store the two tables which works a
View Complete Post