I’ve noticed that there are multiple ways to do SQLite operations (query, insert, update, delete), and some can be faster than the rest. Many websites provide different tips, and some conflict with the others.
-
It seems that using a transaction for bulk insert is somehow faster than doing so in a loop.
How come? What is the best way to achieve best performance when using SQLite? How does sqlite work on Android?
-
Confusing with using InserHelper vs ContentValues, as shown here.
How does the InserHelper work and will it always be faster than ContentValues? Will wrapping it with a transaction speed it up even further?
-
Confusion on other SQL frameworks. I remember that adding indices would boost the performance of queries related to the indices. Is this true for Android too? Is this a good practice?
-
I’ve heard that in some cases, it’s best to not use the UI thread for DB operations. In which cases is this recommended? As in, how slow could DB operation become? If the DB becomes 70MB, does it mean that it will be much slower and UI thread should never handle it?
Transactions involve disk I/O. It is much less expensive to do one larger chunk of disk I/O than lots of little chunks of disk I/O.
Quoting the documentation: “This class allows users to do multiple inserts into a table but compile the SQL insert statement only once, which may increase performance.”
Presumably yes.
Indexes can increase query speed, if you create the proper indexes for whatever queries you are performing. Indexes always decrease insert/update/delete speed, as now those indexes need to be updated. This has nothing in particular to do with Android.
That is impossible to answer in the abstract. This has nothing in particular to do with Android.
Correct.
It is never recommended to perform any disk I/O on the main application thread.
Centuries. Probably by then, something will fail in the device, or it will run out of battery power.
It depends upon what you do with it.
Correct.