ASP Cacheing

Results 1 to 6 of 6

Thread: ASP Cacheing

  1. #1
    Michael Lindley Guest

    Default ASP Cacheing

    I run a large ladder gaming site, and I&#039ve programmed the ladder solely in ASP. We get lots of hits daily and at times we can have upwards of 100 simultaneous connections and it will only go up from here.<BR><BR>The problem I&#039m having is every now and then (just about daily and sometimes multiple times in a day), the server crashes. Anytime an ASP page is accessed it gives a "Server Too Busy" error and quits. This happens only on ASP pages..html pages still load without a problem.<BR><BR>What I have surmised is that it is normally when the hit count gets really high. So I think its related to ASP Cache and/or RAM. The server has 256 RAM, and I&#039m trying to get some more for it b/c I&#039m afraid thats possibly not enough. But last night I stumbled across an article on Microsoft about an error with ASP Cacheing. It would lock up instead of flushing the cache. That looks to be my problem.<BR><BR>They had a fix available by calling. So the server guy called and installed it, which caused lots of problems. We eventually reinstalled IIS4. Basically what I need to know is if any other ASP heavy sites have experienced this problem, what they think may have caused it, and either how they got around it, fixed it, or are planning to do about it.<BR><BR>Sorry for the long post.<BR><BR>Thanks in advance!<BR>Michael Lindley (aka Adrenaline)<BR>Co- Founder - Clan World Network<BR>*****************************<BR>Clan World Network -<BR>Clan World Ladder -<BR>Clan World Tournament -<BR>Clan World League -

  2. #2
    Ian Stallings Guest

    Default RE: ASP Cacheing

    First thing - your permissions are wrong.<BR>Does this look familiar:<BR>sql = "SELECT * FROM " & DBTable & " WHERE rank > 0 and rank &#060; 11 ORDER BY rank"<BR>Set RS = Conn.Execute(sql)<BR><BR>it&#039s your asp code. The u/p for the DB are in their<BR>and that&#039s not ever good.<BR>check out this article for more info on how to set perms<BR>for asp:<BR><BR><BR><BR>But it was cool, because that allowed me to view the<BR>source and fine one error. The recordsets are open<BR>using the above code, but never closed. This will<BR>seriously affect performance. here&#039s an article with more<BR>info on closing recordsets:<BR><BR><BR>A few hints - <BR>Try checking perfmon to see Asp cache hits and memory usage.<BR>If Memory usage is above 75% during peak usage you need to<BR>increase the memory.<BR><BR>If asp cache hits are above 80% or so, try decreasing the<BR>ASP script file cache size in the IIS console until it gets <BR>to a reasonable size.<BR><BR>If you are using an access DB you might want to consider<BR>moving to SQL server. I know this is an expensive option but<BR>SQL servers performance compared to JET/Access is no match <BR>and 100 concurrent users and up is a lot.<BR><BR>But to sum it up - fix the perms, close the recordset, and<BR>check perfmon to find the bottlenecks.<BR><BR>I hope this helps. Keep us posted :)<BR>

  3. #3
    John Harvey Guest

    Default RE: ASP Cacheing

    Just a note,<BR>Our server gets 40,000+ hits a day, and we use ASP for the default page (and others). One of our webs - which generates water level charts - is completely implemented in ASP, uses ADO and an Access DB as well as text files for getting data and also uses an ActiveX control for generating the charts. We get 6000+ hits a day on it (with 256 MB of memory) and it runs fine.<BR>

  4. #4
    Ian Stallings Guest

    Default RE: ASP Cacheing

    But this does not necessarily apply to all applications.<BR>Here at nasdaq-online it&#039s a private site and we only<BR>get 20,000 page views per day, but because of the intense<BR>amount of data being queried etc a 256mb machine would not <BR>be enough. You can only predict performance if you know exactly<BR>how much memory / processor use, etc is being used by each<BR>user. The way you do that is by running performance test.<BR>This is standard procedure on most large sites.<BR><BR><BR>Access is a good app, but SQL server offers better performance<BR>and more scalability.<BR>

  5. #5
    Michael Lindley Guest

    Default RE: ASP Cacheing

    Thanks SOOO much!<BR><BR>Lots of things you said made a lot of sense, its nice to see someone who is willing to help and knows what they&#039re talking about.<BR><BR>The server permissions...I fixed it on my personal server, but when we switched to our sponsor&#039s server, to tell you the truth...I never even though about it. I already emailed the Server Admin.<BR><BR>I&#039m gonna go back through my code and fix the problems, from the highest hit to the lowest. I have one would you handle redirects? Just close all current connections before sending the actual redirect command?<BR><BR>Last thing...hehe<BR>I&#039ve been thinking about going to SQL server, and it is available to us. I&#039m just not sure what problems it will present when switching over. But I think it may be better for the high hit usage we have (and expect). Also..I&#039m intrigued by the Connection Pooling element of it.<BR><BR>Thanks for all the help, I&#039m sure I&#039ll bb :o)<BR><BR>Michael Lindley (aka Adrenaline)<BR>Co- Founder - Clan World Network<BR>*****************************<BR>Clan World Network -<BR>Clan World Ladder -<BR>Clan World Tournament -<BR>Clan World League -

  6. #6
    Sergio Guest

    Default RE: ASP Cacheing

    Ian,<BR><BR>I was very interested in the way you download his source code.<BR>I run a site ( and I would like to know if I have this problem too?<BR>What must I make/know to test this?<BR><BR>TIA<BR><BR>PS as I&#039ll be traveling for 2 weeks, can you send me the answer by email too?<BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts