MySQL Forums :: Performance :: "Sending Data" is taking time post migration from 5.1 to 5.6


Advanced Search

Re: "Sending Data" is taking time post migration from 5.1 to 5.6
Posted by: Peter Brawley ()
Date: March 15, 2017 12:43PM

With 64GB RAM, innodb_buffer_pool_size can be up to 48GB.

The query profiler slows performance and isn't often helpful with optimisation.

Again: Explain is telling you MySQL can't find an index for bct_prod, so it's having to examine millions of rows; that table needs index(prodno,rstate).

Options: ReplyQuote


Subject Views Written By Posted
"Sending Data" is taking time post migration from 5.1 to 5.6 102 Aldrin Davis 03/10/2017 02:41AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 37 Peter Brawley 03/10/2017 12:47PM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 32 SAIKIRAN CHEVITI 03/14/2017 06:40AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 37 Peter Brawley 03/14/2017 09:42AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 36 SAIKIRAN CHEVITI 03/15/2017 08:50AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 36 Peter Brawley 03/15/2017 12:43PM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 21 SAIKIRAN CHEVITI 03/16/2017 02:32AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 33 Peter Brawley 03/16/2017 05:52AM
Re: "Sending Data" is taking time post migration from 5.1 to 5.6 17 SAI KIRAN 03/17/2017 12:08AM


Sorry, only registered users may post in this forum.

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.