Caching in asp.net-mvc

82
votes

I would like to cache my most database heavy actions in my asp.net-mvc site. In my research I have found

But I don't feel I get it yet.
I want to be able to cache my POST request depending on several pars. These pars are in an object. So I would like to cache the result of the following request:

public ActionResult AdvancedSearch(SearchBag searchBag)

Where searchBag is an object that holds (a bunch) of optional search parameters. My views themselves are light (as they should be), but the data access can be rather time consuming, depending on what fields are filled in in the search bag.

I have the feeling I should be caching on my datalayer, rather then on my actions.
How am I supposed to use the VaryByParam in the OutputCache attribute?

4
asp.net-mvccaching
Have you tried with VaryByParam="searchBag.property"? – Eduardo Campañó
no, I haven't. Will try what you say. But how about enumerating several parameters? – Boris Callens
VaryByParam="firstParam;secondParam;thirdParam" – Arnis Lapsa
A little late, but the Enterprise Library Caching Application Block is included in .Net 4.0, so now you can use System.Runtime.Caching's MemoryCache for similar effect. Anywhere too :) – Carl

4 Answers

74
votes

I like to cache in the model or data layer as well. This isolates everything to do with retrieving data from the controller/presentation. You can access the ASP.NET cache from System.Web.HttpContext.Current.Cache or use the Caching Application Block from the Enterprise Library. Create your key for the cached data from the parameters for the query. Be sure to invalidate the cache when you update the data.

66
votes

Or you can be independent of the HttpContext.Current and access Cache from HttpRuntime.Cache :)

12
votes

Often, OutputCaching can be the most fast and efficient, but only when it meets your requirements. No point in having fast efficient if it's wrong! ;)

In this case, it sounds like caching at the data layer is correct because you have complex caching needs. Sometimes, you can combine the two if the set of parameters which control what output is cached is simple.

0
votes

you can use output caching something like this

[OutputCache(Duration = 10, VaryByParam = "empID")]
      public ActionResult GetEmployeeDetail(int empID)
      {
          Employee e = new Employee();
          return Content(e.getEmployeeDetails(empID));
      }

or you can use cache profiles set it in web config

<caching>
<outputCacheSettings>
    <outputCacheProfiles>
        <add name="Admin" 

        duration="86420" varyByParam="none"/>
    </outputCacheProfiles>
</outputCacheSettings>
</caching>

and use this tag
[OutputCache(CacheProfile="Admin")]