MySQL Forums
Forum List  »  Performance

Re: Thread State - Query End
Posted by: Øystein Grøvlen
Date: January 05, 2016 03:09AM


Most of the work in 'query end' state is related to commit processing.

Do you run all update/insert in a single transaction?

I can imagine that if all data is in memory, inserting/updating memory may be fast while forcing the log to disk at commit time may take some time. You can check whether the disk activity is high.

Do you use semi-sync replication? If so, commit will wait for all insert/updates to be replicated to the slave.

Øystein Grøvlen,
Senior Principal Software Engineer,
MySQL Group, Oracle,
Trondheim, Norway

Options: ReplyQuote

Written By
January 04, 2016 11:50AM
Re: Thread State - Query End
January 05, 2016 03:09AM
January 06, 2016 02:28AM

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.