I have select with more then
70 milion rows
I'd like to save the selected data into the one large csv
file on win2012 R2
Q: How to retrieve the data from MySQL by chunks for better performance ?
because when I try to save one the large select I got
out of memory errors
To query more than 1000 rows, there are two ways to go about this. Use the '$offset=' parameter by setting it to 1000 increments which will allow you to page through the entire dataset 1000 rows at a time. Another way is to use the '$limit=' parameter which will set a limit on how much you query from a dataset.
The MySQL maximum row size limit of 65,535 bytes is demonstrated in the following InnoDB and MyISAM examples. The limit is enforced regardless of storage engine, even though the storage engine may be capable of supporting larger rows.
To select first 10 elements from a database using SQL ORDER BY clause with LIMIT 10. Insert some records in the table using insert command. Display all records from the table using select statement. Here is the alternate query to select first 10 elements.
You could try using the LIMIT
feature. If you do this:
SELECT * FROM MyTable ORDER BY whatever LIMIT 0,1000
You'll get the first 1,000 rows. The first LIMIT
value (0) defines the starting row in the result set. It's zero-indexed, so 0 means "the first row". The second LIMIT
value is the maximum number of rows to retrieve. To get the next few sets of 1,000, do this:
SELECT * FROM MyTable ORDER BY whatever LIMIT 1000,1000 -- rows 1,001 - 2,000 SELECT * FROM MyTable ORDER BY whatever LIMIT 2000,1000 -- rows 2,001 - 3,000
And so on. When the SELECT
returns no rows, you're done.
This isn't enough on its own though, because any changes done to the table while you're processing your 1K rows at a time will throw off the order. To freeze the results in time, start by querying the results into a temporary table:
CREATE TEMPORARY TABLE MyChunkedResult AS ( SELECT * FROM MyTable ORDER BY whatever );
Side note: it's a good idea to make sure the temporary table doesn't exist beforehand:
DROP TEMPORARY TABLE IF EXISTS MyChunkedResult;
At any rate, once the temporary table is in place, pull the row chunks from there:
SELECT * FROM MyChunkedResult LIMIT 0, 1000; SELECT * FROM MyChunkedResult LIMIT 1000,1000; SELECT * FROM MyChunkedResult LIMIT 2000,1000; .. and so on.
I'll leave it to you to create the logic that will calculate the limit value after each chunk and check for the end of results. I'd also recommend much larger chunks than 1,000 records; it's just a number I picked out of the air.
Finally, it's good form to drop the temporary table when you're done:
DROP TEMPORARY TABLE MyChunkedResult;
The LIMIT OFFSET
approach slows query down when a size of the data is very large. Another approach is to use something called Keyset pagination. It requires a unique id in your query, which you can use as a bookmark to point to the last row of the previous page. The next page is fetched using the last bookmark. For instance:
SELECT user_id, name, date_created FROM users WHERE user_id > 0 ORDER BY user_id ASC LIMIT 10 000;
If the resultset above returns the last row with user_id
as 12345
, you can use it to fetch the next page as follows:
SELECT user_id, name, date_created FROM users WHERE user_id > 12345 ORDER BY user_id ASC LIMIT 10 000;
For more details, you may take a look at this page.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With