Cache your open connections. Keep your list in most recently used order
and use the most recently used to maximize cache availability.
Sabyasachi Ruj wrote:
I have an application that uses SQLite extensively.
In a part of that application, I need to do the following steps:-
1. I need to create a thread per request basis.
2. Open SQLite connection.
3. Then retrieve data from SQLite and do some calculation.
4. Construct the result and send.
5. Then close SQLite connection.
This type of threads are being created very frequently.
And thats the reason my application is becoming very CPU hungry.
As I have tested a sample application if I do the same steps above in a loop
in a sample program it takes 30% CPU (It is a decent 3.0 GHz processor).
But there if I just take out the sqlite3_open and sqlite3_close, it becomes
0-1%.
So, I want to achieve the same thing in my multi threaded application.
The following ideas came in my mind:-
1. I can share open one SQLite connection and share the connection
between threads with PROPER MANUAL synchronization (so that only one
thread uses the connection at a time).
=> This I ruled out because it will introduce unnecessary
waiting.
2. Create a pool of SQLite connections and allocate them the threads
on demand
basis.
=> This is still in 'idea' phase.
I want to avoid the complexity that it will introduce in the
application.
Is there any way by which I can optimize my application?
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
