outputcache limitations?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Vassilis T. via .NET 247

    outputcache limitations?

    The following piece of code, when on a heavily loaded server (more than 50 ASP.NET pages, most using outputcache with varybyparam, lots of users), will only cache the string - the output is not cached, as if the outputcache is ignored.
    There is available RAM on the server.
    Other pages are cached as expected.
    On the development environment and on a test server, it works fine.

    Are there any limitations to the .NET caching, apart from RAM availability? Should I reduce caching time on other pages, or remove caching from some pages to resolve the problem?

    TIA


    <%@ OutputCache Duration="10" VaryByParam="no ne"%>
    <%
    Response.write( "outputcach e:" & datetime.now.to string("s") & "<BR>")
    Dim atest As String
    if cache("atest") is nothing then
    atest=DateTime. Now.ToString("s ")
    Cache.Insert("a test",atest,not hing,DateTime.N ow.AddSeconds(2 0),Cache.NoSlid ingExpiration,C acheItemPriorit y.High,nothing)
    else
    atest=cache("at est")
    end if
    response.write( "atest string:" & atest)
    %>

    -----------------------
    Posted by a user from .NET 247 (http://www.dotnet247.com/)

    <Id>WKyX1MWf10y QJuroxW6d6A==</Id>
Working...