SQLiteDatabase Android Performance Question

Question

From performance point of view, regardless of other constraints:

What is the cost of opening a SQLiteDatabase in the whole application lifecycle?

Is it worth the effort to open/close everytime needed (and maintaining state)?

RivieraKid · Accepted Answer · 2011-07-26 09:43:28Z

1

If you use SQLiteOpenHelper, it will cache your database object meaning it will be opened only once and closed only once. You can then use getReadableDatabase() or getWriteableDatabase() wherever and whenever is convenient because you will be using the cached database.

SQLiteOpenHelper also makes it really easy to create, open, and upgrade (and with API 11, downgrade too) your database and is the Google recommended way of working with SQLite.

answered Jul 26, 2011 at 9:43

RivieraKid

5,9694 gold badges40 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mat · Accepted Answer · 2011-07-26 09:12:30Z

0

Open the database once => One open/close
Open the database multiple times => Multiple open/close

In 1) and 2), the memory cost is the same while the database is open. So 2) is obviously more expensive with this very reduced set of hypothesis.

answered Jul 26, 2011 at 9:12

Mat

208k41 gold badges407 silver badges423 bronze badges

1 Comment

Sherif elKhatib Over a year ago

but there must be some cost for the database being open the whole process cycle?

Collectives™ on Stack Overflow

SQLiteDatabase Android Performance Question

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related