CODEWITHSUNDEEP
asp.netmemory-management
rlb.usa
rlb.usa

Reputation: 15041

Storing large amounts of data locally

I'm experienced with ASP.NET but some of my knowledge is a little shaky. I'm creating an application that uses services to get large portions of data. I then want to filter it with LINQ to what I need. This data rarely changes, but I know there's too much of it to fit in Session.

How can I store rarely-changing , large amounts of data in memory? Would this be suitable for Application variables?

Upvotes: 3

Views: 1267

Answers (2)

Sean Glover
Sean Glover

Reputation: 1786

Instead of caching the source data, consider using HTTP caching via ASP.NET Output Cache or memcached to store the rendered output itself. ASP.NET OutputCache can be tuned to work on specific ASP.NET resources and there are many ways to invalidate the cache explicitly if need be. See the following MSDN resources for more information.

ASP.NET Caching Overview

Output Cache Configuration

OutputCache Attribute for ASP.NET MVC

Upvotes: 1

Eric J.
Eric J.

Reputation: 150238

You can store large amounts of fairly static data:

  • In the HttpContext.Cache
  • In a private static field of a C# class. Wrap the variable with an public get property that can initialize the static field. The static field will need to be initialized when the app first starts, and any time the app domain is recycled by IIS.

HttpContext.Cache

Pro's

  • Configurable cache expiration policy.
  • Designed specifically for the ASP.Net environment

Con's

Static Field

Pro's

  • Complete user control over cache expiration.

Con's

  • Any cache expiration must be explicitly programmed. No built-in expiration support.

Upvotes: 1

Related Questions