That's incredibly slow. I pull 1000 records through PHP in 1 second on a P4 2.4 Ghz. Are you pulling the entire recordset and then limiting it in your app code? Or are you using a limit clause in the DB?
Also, Peter's point about indexing might help. Without specific SQL examples, it's difficult to suggest optimizations. Mysql does have a great section in their manual re: optimizing select queries. Scott. On Wed, 9 Mar 2005 16:10:19 -0500, Peter J Milanese <[EMAIL PROTECTED]> wrote: > Does the app display all 1000 rows at once? Does your app require all > fields? Only retrieve what you need for the page. If the app displays all > 1000 rows, it may remain slow depending on how you get them (order, group, > function) and indexing.. Also, the link and disk may matter depending on > the size of the row. I do not know what you could do on the client side to > help. > > ------Original Message------ > From: Carlos Savoretti > To: MySQL List > Sent: Mar 9, 2005 5:49 PM > Subject: Optimizing a big query... > > Hi all: > > I programming a GUI which retrieve big tables oftenly. > > So, I retrieve chunks of 1000 rows and paginate then > > to browse the entire table. It works fine, but it's rather > > slow. > > I would like to know if I could set some option thru > > mysql_option() to optimize the client side (mysql-client-3.23.58) > > and what is the the recommended value to clamp the `page' for a > > gui app. (For 1000 rows it uses about 12 seconds). > > Thanks a lot... > > -- > Carlos Savoretti <[EMAIL PROTECTED]> > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > ----------------- > Sent from my NYPL BlackBerry Handheld. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
