The other thing I have found, is do EVERYTHING possible to reduce transaction time. Optimize code, and make sure you database is returning results to witango as fast as possible.

If your database is slowing down due to load, you can add 20 witango servers, and you won't notice any improvement. A witango thread will hog/eat the cpu while waiting for results.

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Oct 13, 2006, at 8:58 AM, Ian Daniel wrote:

Ok .. we have some seriously overloaded servers.
 
The Witango 5.x threadcount is by default set at 15.
 
On a Win2k3 server with 2 Gb of ram, what is a safe maximum to adjust this to?
 
 
Ian Daniel, A.Sc.T.,     President
New Creation Consulting & Information Management Inc.
# 505,  889 West Pender Street, Vancouver, BC  V6C 3B2  Canada
======================================================
[EMAIL PROTECTED]                http://www.ncol.com       
Ph: (604) 806-6265  ext 110         Fax: (604) 806-6269 
 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to