MySQL Forums
Forum List  »  InnoDB

Re: high concurency issue with read-write on mysql table
Posted by: Peter Brawley
Date: June 12, 2017 11:09AM

InnoDB doesn't lock a whole table just to delete some rows. You might want to run Show Processlist to see what else is going on.

Big deletes chew up a lot of resources. Running Show InnoDB Engine status during the delete might show just how much. If an average row in your table takes up 200 bytes, innodb_buffer_pool_size needs to be > 4GB for your 20M rows to fit in memory. How much RAM does the machine have, what is innodb_buffer_pool_size? It should be about 75% of the RAM that's available to MySQL.

A common way to improve the performance of big deletes is chunking, see http://mysql.rjweb.org/doc.php/deletebig.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: high concurency issue with read-write on mysql table
77
June 12, 2017 11:09AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.