Reconnect Very Slow On Windows 7 Prof 32 Bit

[gerkoJansen]

When starting SQLYog initially the connection works perfect and SQL statements are executed fast.

However after idling for a little while it takes about 30 seconds or more to execute the query. I suspect it's trying to reconnect to the server.

I find this really frustrating since the program idles on my desktop daily using it when i need it.

I connect the regular way using the MySQL tab on default port.

[peterlaursen]

What program version are you using? Do you sue SSH-tunnel?

Note the additions in 8.13:

http://www.webyog.com/blog/2009/08/14/sqlyog-813-has-been-released/

Quote:

* Added an option for user to specify the timeout setting for the session (note: it will work with MySQL 4.1 and up only as earlier versions do not support SESSION variables). Please see detailed note below.

* SQLyog reconnects are now coded differently (now the MySQL API reconnect option is used – before it was our own code).

Please try to use the option to set session timeout in the connection settings(values up to 28800 are valid) and also please tell the result from “SHOW GLOBAL VARIABLES LIKE '%timeout%';” on this server .

A related Blog post: http://www.webyog.com/blog/2009/09/02/“mysql-server-has-gone-away”-part-2-session-timeout/

[gerkoJansen]

Thanks for your reply.

I will give this a try. I am using version 8.71.

The results of the query:

connect_timeout 10

delayed_insert_timeout 300

innodb_lock_wait_timeout 50

innodb_rollback_on_timeout OFF

interactive_timeout 28800

net_read_timeout 30

net_write_timeout 60

slave_net_timeout 3600

table_lock_wait_timeout 50

wait_timeout 28800

Is the connect timeout perhaps to low?

Thanks.

[peterlaursen]

I believe that connect_timeout will not make a difference. It defines how much time the the complete process of establishing connection between server and client may take. If it is exceeded the connection will not be established. If connection is getting established it is sufficient.

It looks like this is not a MySQL or SQLyog problem but a network problem. Maybe you could try with another client?

[Author]

Posts