MySQL Bugs: #7277: Slow display times for larger resultsets

Bug #7277	Slow display times for larger resultsets
Submitted:	14 Dec 2004 16:42	Modified:	16 Nov 2005 14:28
Reporter:	Wesley Hampton	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.3a-1	OS:	Linux (SuSE 9.1)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
I installed the .rpm for SuSE 9.1 and the program starts up fine, however, querying increasingly larger tables results in increasingly slow return times.  The time that Query Browser shows in the status bar at the bottom (xxxx rows fetched in x:xx.xxxx) says that it retrieved the results very quickly, however the time it takes query browser to display them is very slow.  It seems to make a huge difference in display time if you limit the number of fields returned, but not a big difference in the time that Query Browser reports the rows were fetched in.  The larger the resultset, the longer it takes to display the results.  This was not an issue until this version that I am aware of.  I have tested this on multiple machines all running SuSE 9.1 and have been able to duplicate the problem.  This version in Windows XP does not have this problem.  Some example test times are below showing what Query Browser reports versus the time it actually takes (roughly) to display the resultset.  All tests were on the same table which has 26 fields consisting of a mix of integer and text fields, by limiting the resultset through the SQL statements (LIMIT  50, LIMIT 100...etc.  Look especially at the last two lines of data.

50 rows fetched in 0:00.1656 - (displayed in <1s) (26 fields of data)
100 rows fetched in 0:00.1683 - (displayed in ~1s) (26 fields of data)
500 rows fetched in 0:00.1863 - (displayed in ~3s) (26 fields of data)
1000 rows fetched in 0:00.2134 - (displayed in ~5s) (26 fields of data)
1500 rows fetched in 0:00.2254 - (displayed in ~7.5s) (26 fields of data)
2000 rows fetched in 0:00.2412 - (displayed in ~9.5s) (26 fields of data)
2500 rows fetched in 0:00.2583 - (displayed in ~12s) (26 fields of data)
2500 rows fetched in 0:00.1404 - (displayed in <1s) (1 field of text data)

How to repeat:
Query a large table and adjust the fields returned as well as limit the rows returned.

Version 1.1.4-1 does not fix this bug, just for the record.  In fact, I ran the same 2500 row query (with 26 fields) as explained in the main bug report, and this time it took almost 28seconds to display!!  I believe it may actually have gotten worse!  Anyway, hope this information helps somehow.

Version 1.1.4-2 SuSE 9.1 rpm does not fix this problem, just for reference.

Should be fixed now that it has been upgraded to use gtkmm-2.6