@g-oku Based on the test scenario you describe, it is quite possible that you are running into an expanding database due to the repeated inserts, updates, and drops. SQLCipher does not automatically vacuum the database for you. As noted in the final point of the performance post, performing periodic vacuum operations will keep the database compact, particularly when you are performing large deletes, multiple updates etc. Can you try adding an execSQL(“VACUUM”); operation following the table drop, then re-running the test?