On 3/6/06, Bryan Sant <[EMAIL PROTECTED]> wrote: > Just so I don't make assumptions... The Linux box is connecting to a > seperate MSSQL server over the network. Likewise, the 2K3 server is > connecting to a seperate MSSQL server over the network. Correct? That is correct, SqlServer is running on a seperate server, all by it's little lonesome, and for the record, it's cpu utilization doesn't differ between the windows and the linux server.
> When you get a chance to run your app in Linux under some load execute: > > uptime > ...and... > vmstat > ...and... > netstat -s > ...and... > top -n 1 > ...as well as the original... > netstat -tn | grep -v ESTABLISHED > > I think when you run the above commands (please send the output of > each) we're going to find out that the CPU is waiting on something > most of the time. My guess is that you are hitting your kernel's > currently set TCP/IP stack limits on max open TCP connections and the > TIME_WAIT problem I described before is the issue -- or -- for > whatever reason, you're JDBC connection to the MSSQL server isn't > retrieving data as fast as the 2K3 server is. Thanks for the info - I'll run these the next time we switch to the linux server and see what it tells me. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
