For starters, compare timings between running a query between the machines and one local to the machine. Use the command line client, not your web server. See if there is a significant time difference. If there is, there is probably something wrong on your network. If not, then you should check your web server for bottlenecks.
Of course, network slowdowns could come up if the machines are on separate switches, one or both are not running full duplex, the switch isn't set to full-duplex, network errors (i.e. due to damaged or poor quality cables). And naturally, checking that you are not running at the full capacity of your network.


Bottom line, put in timings in your code to find out where the bottleneck is. Monitor your machines for cpu, memory and I/O usage levels. You need to find where the bottleneck is before you start playing with server variables.


On Apr 21, 2005, at 3:47 PM, Rob Brooks wrote:

Hello, we have a web based application where the mysql server runs on a
separate box from the code. The 2 boxes are on the same subnet so there
really shouldn't be any latency issues(emphasis on shouldn't .) but we're
trying to track down some timeout glitches in the application. I was
wondering what things I might look at as far as server variable settings
that might be pertinent to having the mysql server on a different box from
the code.




server 4.0.2 on darwin6.8



Thx

Rob


--
Brent Baisley
Systems Architect
Landover Associates, Inc.
Search & Advisory Services for Advanced Technology Environments
p: 212.759.6400/800.759.0577


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to