lag after executing queries in Browser

Every time I execute even the most straightforward of
queries, the whole
browser hangs for 2-3 seconds and then submits the query to
the server.

This makes the application a hell of lot less productive,
and makes fast
queries times take time.

I have the latest 1.2.10 version of the query browser in
windows XP. I have
noticed this issue does not exist in the linux version. What
should I do?

I have this problem thousands of times.

The problem is the way Query Browser executes queries.
Each time you request a query to be executed, IT OPENS A NEW
CONNECTION
This is true whether you drop a table, add a stored
procedure, anything.

Here is the big question : Are you accessing a MySQL
database running locally,
another machine running Windows, or another machine running
Linux ???

IF you accessing MySQL running on another machine with
Linux,
is logging into Linux fast or slow ??? I ask this because
network
congestion or activity has a direct bearing on how fast each
MySQL
connection gets established from Query Browser.

Try rebooting Linux where MySQL is running. If that works,
then
configure Linux to authenticate as fast as possible going
forward.

----- Original Message -----
From: "Thanos Panousis" <pthanosgmail.com>
To: gui-toolslists.mysql.com
Sent: Monday, March 5, 2007 9:47:56 AM (GMT-0500)
Auto-Detected
Subject: lag after executing queries in Browser

Every time I execute even the most straightforward of
queries, the whole
browser hangs for 2-3 seconds and then submits the query to
the server.

This makes the application a hell of lot less productive,
and makes fast
queries times take time.

I have the latest 1.2.10 version of the query browser in
windows XP. I have
noticed this issue does not exist in the linux version. What
should I do?


-- 
MySQL GUI Tools Mailing List
For list archives: http://lists.mysql.c
om/gui-tools
To unsubscribe:    http://li
sts.mysql.com/gui-tools?unsub=bondyahoo.com

Well, I am glad I am not the only one.

The funny thing is there was no mention of the problem on
the net, at least
not one I managed to google.

The local host that the browser is running is windows, and
so is the remote
host. You mention that the lag is due to the connection
establishment. If
the browser is running in linux and I connect to the same
windows server,
this lag does not happen. It only occurs on every windows
machine in the
company.

It is a very frustrating problem, needless to say. Why does
it open a new
connection every time? Isn't it mysql 101 that you don't do
that? Can't it
just close (and then reopen on a subsequent query) the
connection after some
(long) timeout?


On 3/5/07, Rolando Edwards <redwardsswmx.com> wrote:
>
> I have this problem thousands of times.
>
> The problem is the way Query Browser executes queries.
> Each time you request a query to be executed, IT OPENS
A NEW CONNECTION
> This is true whether you drop a table, add a stored
procedure, anything.
>
> Here is the big question : Are you accessing a MySQL
database running
> locally,
> another machine running Windows, or another machine
running Linux ???
>
> IF you accessing MySQL running on another machine with
Linux,
> is logging into Linux fast or slow ??? I ask this
because network
> congestion or activity has a direct bearing on how fast
each MySQL
> connection gets established from Query Browser.
>
> Try rebooting Linux where MySQL is running. If that
works, then
> configure Linux to authenticate as fast as possible
going forward.
>
> ----- Original Message -----
> From: "Thanos Panousis" <pthanosgmail.com>
> To: gui-toolslists.mysql.com
> Sent: Monday, March 5, 2007 9:47:56 AM (GMT-0500)
Auto-Detected
> Subject: lag after executing queries in Browser
>
> Every time I execute even the most straightforward of
queries, the whole
> browser hangs for 2-3 seconds and then submits the
query to the server.
>
> This makes the application a hell of lot less
productive, and makes fast
> queries times take time.
>
> I have the latest 1.2.10 version of the query browser
in windows XP. I
> have
> noticed this issue does not exist in the linux version.
What should I do?
>
>