Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: Java
Expertise: Intermediate
Sep 5, 2017



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Disabling AutoCommit in JDBC

Only once the development part of the project is complete do we tend to look at the performance of our application's interaction with the database and realize that the transactions are relatively slow. A potential source for bottleneck could be the autoCommit feature of your connection to the database.

Most of the time, database operations are time-consuming when compared to in-memory operations. In addition, such actions add to the overhead. Ideally, instead of auto committing after every insert, it is ideal to commit once the transaction is complete.

For example, instead of committing every insert, while you are reading from a file and inserting records, it is better to commit after the entire file is read and the database updated. There are numerous other cases where you can consider this options.

//Connect to the database 
Connection connection = DriverManager.getConnection( host, username, password );
connection.setAutoCommit (false); // Setting the auto commit to false. This will ensure that commit is not automatic

//You can enable it by passing true subsequently when you think it is appropriate.
M S Sridhar
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date