StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSQLite in Java: Ways to optimize my queries to make them return faster?
text
Body
copied!<p>I am creating an application in Java that uses SQLite to store and search the data in a database.</p> <p>I am not sure if I am approaching this problem in the most efficient way and I figured someone here could help me out with that.</p> <p><strong>Background info:</strong> My Java application parses .PDF files using a library that can transform the raw text from the PDF files to a StringWriter. I then parse the resulting data and get the info I need to create some new rows in my database. The resulting tables are very large, though, as there are about 900 PDF files to parse. Just to give you an idea of how large I'm talking, one of the table ends up with about 145000 rows, another with 1550 rows, and the others (3 or 4 other tables) with between 75 and 750 rows.</p> <p>Everything works fine, but I'm not sure if Icould lower the required time to create the tables and stuff. So far, on my laptop computer, it takes 41 minutes to create everything the first time through (though everything runs from an USB flash drive... I'll test it on a HDD later). It takes 1.5 minutes when I run it again since it checks if the file has already been parsed and it doesn't re-create everything. I don't need it to be a HUGE improvement since ideally I'd run this program only once a week with about 30 files or so, but still, I'm wondering why it is so slow with 900 files; if it's the code that is parsing the files that is slow or if it's bad practice on my end in the SQLite part. (I'm testing it with all the files created in the last year, which is why I have that many) </p> <p>So, what are the best practices to improve performance with SQLite in Java? Would it make a noticeable difference to put autocommit to false and to commit only once everything is created? Is there a way to create statements or to test if data already exists in a more efficient manner?</p> <p>I don't have my code with me, but the queries look kinda like this:</p> <pre><code>public static void insertScores(String league, int playerID, int score, String date) { PreparedStatement ps = new PreparedStatement("INSERT INTO Scores(?,?,?,?)"); ps.setString(1, league); [...] ps.executeUpdate(); } </code></pre> <p>On other queries, I test to see if the row already exists using something like this:</p> <pre><code>public static void insertScores(int playerID) { ResultSet rs = null; PreparedStatement ps = new PreparedStatement("SELECT * FROM Scores WHERE ID = ?"); ps.setInt(1, playerID); rs = ps.executeQuery(); if(!rs.next()) { [code like in the first example] } } </code></pre> <p>Keep in mind that syntax errors are because I'm only typing this by heart since I don't have my code with me.</p> <p>Just by seeing those examples and reading what I had to say, does anyone have any idea how to improve performance in my SQL statements?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload