| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Mark Hazen | Date: | June 20 2002 2:03am |
| Subject: | 3.23.51 LIMIT efficiency problem | ||
| View as plain text | |||
I am using MySQL 3.23.51 on Linux. I have a fixed-length table with 45 million rows. It appears MySQL has an efficiency issue with the LIMIT command. When I run SELECT a FROM b LIMIT 0, 1000000 <-- that's one million The query finishes almost immediately. But when I run 20 million rows into the dataset, it really slows down. (pretend the commas aren't there) SELECT a FROM b LIMIT 20,000,000, 1,000,000 Why would it slow down? We're dealing with a fixed-length table here. This is just mathematics to figure out where row 20,000,000 is. Confused, Mark
| Thread | ||
|---|---|---|
| • How to convert an Access 2000 Database on PC to a MySQL onUnix Platform | Liqiang Feng | 19 Jun |
| • Re: How to convert an Access 2000 Database on PC to a MySQL on UnixPlatform | Oliver Vecernik | 19 Jun |
| • RE: How to convert an Access 2000 Database on PC to a MySQL on UnixPlatform | michael johnson | 20 Jun |
| • 3.23.51 LIMIT efficiency problem | Mark Hazen | 20 Jun |
| • Re: 3.23.51 LIMIT efficiency problem | Dan Nelson | 20 Jun |
| • Re: 3.23.51 LIMIT efficiency problem | central | 20 Jun |
| • Re: 3.23.51 LIMIT efficiency problem | Benjamin Pflugmann | 20 Jun |
