Web site memory limit

Discussion in 'ASP.NET / ASP.NET Core' started by Bruce, Jan 12, 2006.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Bruce

    Bruce DiscountASP.NET Staff

    Huckster

    It is not possible for us to increased the allocated memory any further.

    Honestly specking, I think 100MB process is already generous. Pop the task manager in your own computer and you'll probably see that you won't have much process over 100MB (of course, unless you have some application that leaks memory).

    For most asp.net applications hosted with us (and we host thousands), most do not use more than 40MB.

    My recommendation:

    1) Check your application to see where all the memory are being assigned to. In general, with ASP.NET application, if you load a file or Access database, the whole file get suck into memory.

    2) Consider switching to MS SQL Session. This will at least keep your user logged in after the proc recycled.

    Hope this helps.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
    Bruce, Jan 12, 2006
    #1
  2. huckster

    huckster

    I've been having some back and forth with tech support over a server memory related issue I've been experiencing. It all started when I noticed that intensive queries were causingmy site'ssession to reset. All my user's who were logged in would immediately be kicked out because Itrack my users'login status using a session variable (pretty typical.)

    Basically, I think that the problemcomes down tothis: whenmyaccount'sRAM usage hits 100MB, DiscountASP.net is set up to automatically recycle the process running my web site. As a result, I see all my session variables go up in smoke.

    Since realizing this problem, I decided to offload much more of the processing of my app to SQL Server. Instead of storing entire tables in the Context.Cache() and Context.Session() objects, I store only the basic UserIsLoggedIn boolean variable in the Session, and retrieve the remaining info through OleDbDataReaders()and useaggregate SQL functions wherever possible to avoid lots of round trips to the server.

    I am building my processing-intensive reports once per day and then caching the results in a flat-file structure and pulling out the reports with a simple SELECT(*) -- so now I don't have to doany fancy report building on the fly.

    Although these steps have greatly improved things, I still occasionally (1-2 times per day)experience the same problem where the session drops. Not surprisingly, this happens right after my daily report generator runs, whichis fairly processing intensive because it is building reports for some 300+ users.

    I am at a loss for what else can be done. Does anyone have any suggestions? Is there a way I can montior how much RAM myaccount isusing? It does not appear that DiscountASP.net offers any way for me to upgrade, which breaks my heart because I like everything else about the hosting package ... just seems like I need moreRAM. Has anyone else experienced this? What do you recommend?

    I have about 350 users, but at most 5% of those users are logged on at once. So even if we are talking about 20 concurrent users, they are only going to be running the simple flat-file report ... this shouldn't be too much for my account to handle, should it???

    Sorry for writing such a long post.

    Thanks,
    Huckster
     
    huckster, Jan 12, 2006
    #2
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page