Last post Apr 04, 2009 02:26 PM by WildMetrix
Apr 04, 2009 02:26 PM|WildMetrix|LINK
During the design phase of developing an ASP.NET application it is vital developers utilize the ASP.NET Cache feature. A good “rule of thumb” when deciding when to use the caching feature is when data, pages, parts of pages are used more than once. More
specifically any data that is general in nature and does not change depending on specific user requests is a perfect scenario for caching. This saves on time and overhead for collecting and creating reusable objects. However, it is possible to use too much
caching. For example, on a 32-bit application process you do not want to use more than 800MB of private bytes. This is an important consideration when designing your application to avoid those pesky “out of memory” errors. Use but do not overuse. [more]
There are three types of cache in the ASP.NET framework to consider:
With a little time spent on planning during design meetings can save you a lot of “head scratching” down the road. The ASP.NET Cache API makes implementing caching easy for programmers and the benefits gained in terms of performance will save on support
costs in the future.