In the last couple of weeks, our workbench has suddenly become very slow for even the simplest of tasks.
Here's a copy of a Action Output:
SELECT * FROM table LIMIT 0,100 | 100 rows(s) returned | 0.078 sec / 0.015 sec
All seems great there, but it took 20 seconds to return this result! Even though it says its duration and fetch were minimal, it's taking forever for Workbench to return it.
Here's a list of information / oddities we've found during troubleshooting:
1.) The DB and return times themselves are fine... website humming along, so doesn't seem to be a DB problem.
2.) Multiple other methods of returning the query results, SSH / command line, other clients (Toad), etc. all work just fine and extremely quick. We've assured that the settings are exactly the same for all.
3.) This only began to happen a few weeks ago, though nothing major occured.
4.) The problem occurs on either the latest workbench or 5.2. So not version dependent.
5.) The problem occurs for multiple users, so not installation dependent.
6.) Other connections, say to our production environment, work just fine, so it doesn't appear to be an IP restriction or something.
7.) We do have lots of other tables and information, but not a ridiculous amount. Plus, there's probably a lot more information on the production environment.
8.) Workbench is giving no visual indication about what it's thinking.
So we're really at a loss. There are things that refute the notions of client, connection, installation, or DB problems. At this point, we really have no idea what's going on, but workbench is basically unusable for us.
Anyone have a lead or thought? Is there any way to see what Workbench is "thinking"?
Thanks,
Jeremy
Here's a copy of a Action Output:
SELECT * FROM table LIMIT 0,100 | 100 rows(s) returned | 0.078 sec / 0.015 sec
All seems great there, but it took 20 seconds to return this result! Even though it says its duration and fetch were minimal, it's taking forever for Workbench to return it.
Here's a list of information / oddities we've found during troubleshooting:
1.) The DB and return times themselves are fine... website humming along, so doesn't seem to be a DB problem.
2.) Multiple other methods of returning the query results, SSH / command line, other clients (Toad), etc. all work just fine and extremely quick. We've assured that the settings are exactly the same for all.
3.) This only began to happen a few weeks ago, though nothing major occured.
4.) The problem occurs on either the latest workbench or 5.2. So not version dependent.
5.) The problem occurs for multiple users, so not installation dependent.
6.) Other connections, say to our production environment, work just fine, so it doesn't appear to be an IP restriction or something.
7.) We do have lots of other tables and information, but not a ridiculous amount. Plus, there's probably a lot more information on the production environment.
8.) Workbench is giving no visual indication about what it's thinking.
So we're really at a loss. There are things that refute the notions of client, connection, installation, or DB problems. At this point, we really have no idea what's going on, but workbench is basically unusable for us.
Anyone have a lead or thought? Is there any way to see what Workbench is "thinking"?
Thanks,
Jeremy
