A quick thing to check is that DNS lookups are timing out on connect.
If you don't have DNS on your local subnet, the server may be doing
reverse lookups..
Otherwise, you should definitely profile your code.
On 4/21/05, Brent Baisley <[EMAIL PROTECTED]> wrote:
> For starters, compare timings betw
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
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
