Use @SERVERSTATUS's CacheBytesUsed to see how much data is in your cache. Do a little math with @@system$cachesize and you can determine a percentage of usage.
In my experience, I up my cachesize whenever I see that value increase over 70%. This generally removes the need for Witango to determine that an incoming cacheable item will exceed the cachesize, determine the oldest file in the cache and clear that file (a time consuming process). Also, look at your witangoevents.log, Witango will tell you when it's removing old items from the cache to make room for new ones. Since memory is relatively cheap nowadays most servers seem to have 1-2GB, in this situation, setting the cache for 25-50 MB shouldn't be a problem, and should cover your needs easily. Robert -----Original Message----- From: Bill Conlon [mailto:[EMAIL PROTECTED] Sent: Friday, February 11, 2005 4:39 PM To: Witango-Talk Subject: Witango-Talk: Sizing the cache I just added another application to my server, and have notice witangod using more cpu in top. Partly, this is a function of the new app and its user load. But I'm curious about whether I need to increase my cache. Does anyone have any tips or rules of thumb on setting the cache? Are there any tools available to monitor cache hits or otherwise assist in tuning? I'm still running witango 5 on linux. thx. bill ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
