I am wondering if it isn't more of a scoping issue. If you are using a lot of USER scoped variable then those are being stored on the server and if they are not purged this cache of variable can grow quite large and affect performance. Make sure to <@PURGE them when done.
Also referring to variable without scope (ie. @@Imavar instead of @@Requet$Imaver) can start to slow performance as I use Local/Request scope because they purge themselves. So I don't have to rememeber to purge them ;-) Cookies can off load a lot of this variable storage The sooner the app can process the soon it can release the thread. Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Authorized MDaemon Mail Server Reseller http://www.pcforge.com/AltN.htm -----Original Message----- From: Ted Wolfley [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 12:35 PM To: '[EMAIL PROTECTED]' Subject: Witango-Talk: Site slowing down Hi, There is a noticeable slowness when there is a increase in usage of our web site. Will increasing the threadPoolsize setting help this? It is now set at the default of 20. After we reset the Rtango2000 service, speed returns to normal. Ted ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
