Ok I get it now. Yes we are using a single db connection object, But few questions, 1) how would making sqlite3 single thread that improve the performance? Is there a special advantage in this mode than the multithread one? 2) Will it not block (wait or give a SQLITE_BUSY) the multiple thread of the app (in our case glusterfs IO threads) as now they have to wait for the single thread to complete the task?
~Joe ----- Original Message ----- From: "Eduardo Morras" <emorr...@yahoo.es> To: sqlite-users@sqlite.org Sent: Monday, November 24, 2014 12:29:33 AM Subject: Re: [sqlite] Using Sqlite3 as a Change Time Recording Data Store in Glusterfs On Sat, 22 Nov 2014 11:01:45 -0500 (EST) Joseph Fernandes <josfe...@redhat.com> wrote: > Thanks Eduardo. > > Answers inline JOE>> > > a)If you use Sqlite in single thread, compile it without thread > support. > JOE>> We are running it in multithread mode, as the database will be > JOE>> fed by multiple File IO thread. Yes and no, your app can be multithread, but if only one thread has the sqlite3 pointer, you can use single thread sqlite3. This way, you have multiple working threads and one sqlite3 dedicated thread that recives the data to write and the data queries. --- --- Eduardo Morras <emorr...@yahoo.es> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
