I might be seeing something like this on my servers, but I can't be sure. Typically purging the cache is a harmless function. If you always see high load after a purge, you should evaluate your hardware. Once in a while I do see a pinned CPU issue. This has only started recently (post moving to 062) and I haven't had a chance to hunt down the cause yet, but this is a possibility.
I do want to mention that purging the cache is sensitive to path, so if you can group like files in a folder, you can minimize the effort of @PURGECACHE. Robert Shubert Tronics Problem #2 - Major performance problems after doing an @purgecache. We've just launched a new site, that is getting quite a bit of traffic. on our Witango 062 box. running Windows NT. Part of my application needs to clear the tango cache, in order to "publish" changes to the websites. When this is done on this machine, the following is happening. 1. The server gets very busy (100% cpu util) handling incoming requests for tafs and tcfs that aren't cached. 2. It never recovers, because the incoming requests cause everything to snowball. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
