Bug #72946 Workbench display is very slow to update after query completes.
Submitted: 10 Jun 2014 22:39 Modified: 3 Feb 2015 1:30
Reporter: Kevin Hollingshead Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.1.6.11834 OS:Windows (Windows 8 on Parallels)
Assigned to: CPU Architecture:Any
Tags: screen update, slow, workbench

[10 Jun 2014 22:39] Kevin Hollingshead
Description:
V.6.0.11834 is also too slow to use. When I checked for updates via the Help menu it tells me I have the latest. It's definitely within workbench as the queries take negligible time, yet it takes about 15 seconds to populate the 11 visible rows in the result area (multiple passes) for each of the three queries below.

I'm running on Windows 8 under Parallels on a MacBook Pro Retina. 

15:06:12|select * from participants LIMIT 0, 1000|260 row(s) returned|0.000 sec / 0.000 sec

15:06:12|select * from moves where participant_xid = '...' LIMIT 0, 1000|186 row(s) returned| 0.031 sec / 0.016 sec

15:06:17|select * from sleeps where participant_xid = '...' LIMIT 0, 1000|265 row(s) returned| 0.031 sec / 0.000 sec

How to repeat:
Any query, it would seem.

Suggested fix:
Looks like you may be using a deprecated grid control? If there's any other info I can get please let me know.
[11 Jun 2014 1:20] MySQL Verification Team
Thank you for the bug report.
[19 Jun 2014 21:03] Alfredo Kojima
15s is very odd, I've never seen something like that. Does that happen for any query, even single column resultsets with just a number? 
Do your queries contain long strings?
[19 Jun 2014 22:54] Kevin Hollingshead
Hmmm...re: "any query", not sure. DB isn't my primary task, I normally do select *'s, but it does show this problem on tables with just two columns. Results are left to the default cap of 1000 rows.

Re: "long strings", if 160-ish characters or less is long then yes.

One odd thing is that the delay happens independent of the initial query when just scrolling the result set up and down.
[31 Oct 2014 3:44] Bill Collins
I'm having a similar problem.  I updated to MySQL Workbench 6.2.3 and now it takes 20 seconds to return a query of all the columns (SELECT * FROM ....).  The table is only 46,000 rows - no long strings.  This wasn't a problem in V5.

If I use another tool, like Toad, there is no problem running the same query.

The more restrictions I put in the query, the faster it runs, even when returning almost all of the rows.
[3 Feb 2015 1:30] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.2.5 release, and here's the changelog entry:

The results grid rendering functionality was improved. Before, some
queries took an unreasonable amount of time to display the results.

Thank you for the bug report.
[12 Feb 2015 22:23] Albert Wang
Can the fix in coming 6.2.5 resolve the same problem in Linux version? Thank you.