MySQL Forums
Forum List  »  Connector/J, JDBC and Java

Advanced Search
New Topic

Re: Performance Impact of rollback() Immediately after a commit().
Posted by: Mark Matthews
Date: April 18, 2018 02:03PM

Hi!

It's not a no-op, because it's not always possible to determine the transaction state on the other side of the connection. You'll always pay a latency cost for issuing a rollback() against a MySQL JDBC connection. It is not free, but it is small though, "real" work will dwarf the amount of time spent issuing it.

- Mark

Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Written By
Posted
Performance Impact of rollback() Immediately after a commit().
Scott Andrews
April 18, 2018 07:47AM
Re: Performance Impact of rollback() Immediately after a commit().
Mark Matthews
April 18, 2018 02:03PM


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.