I had a look at our 2003 servers and they are at 15 too, sorry can't help there ):
did your servers all of a sudden get overloaded?
If so maybe something else is to blame such as windows update screwing a config item up (a windows update once turned off our http compression and cost us a few hundred dollars) or some new software? Or perhaps you should check your sql query execution times to see if maybe you just need to index some tables better or optomize a query, or something like that.
It sounds pretty urgent though so you may not have the option of investigation eh? :P
if you do have some time, one thing we do on our servers is have a crontab event that fires every 15 minutes and logs the values of <@serverstatus> as well as datasource statistics and this lets us view trends on the server (especially when graphed).
That combined with a user activity log and maybe even some benchmark logs for involved processes such as reports, you can get some mean research done and find your bottlenecks.
On 10/13/06, Ian Daniel <[EMAIL PROTECTED]> 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.comPh: (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
