Re: [sqlite] BACK API Questions

2009-12-16 Thread Max Vlasov
> > For ex, If I ran for 200,000 inserts, first 20,000 inserts were done in 9 > secs, but last 20,000 inserts (from 180,000th to 200,000) took almost 110 > secs. It is more than 10 times than what it was initially. These results > were consistent across all iterations of simulation I did. > > I

Re: [sqlite] BACK API Questions

2009-12-16 Thread David Bicking
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Max Vlasov > Sent: Wednesday, December 16, 2009 2:38 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] BACK API Questions > > On Wed, Dec 16, 2009 at 9:30 AM, Raghavendra Thodime > <rthod...@sipera.co

Re: [sqlite] BACK API Questions

2009-12-16 Thread Raghavendra Thodime
: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Max Vlasov Sent: Wednesday, December 16, 2009 2:38 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] BACK API Questions On Wed, Dec 16, 2009 at 9:30 AM, Raghavendra Thodime <rthod...@sipera.

Re: [sqlite] BACK API Questions

2009-12-16 Thread Max Vlasov
On Wed, Dec 16, 2009 at 9:30 AM, Raghavendra Thodime wrote: > I did try using batch of transactions with synchronous=OFF PRAGMA set. The > performance improved slightly. But as db file started to grow larger and > larger in size, the performance degraded considerably. Is it

Re: [sqlite] BACK API Questions

2009-12-15 Thread Raghavendra Thodime
- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Max Vlasov Sent: Tuesday, December 15, 2009 3:56 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] BACK API Questions > You don't need to modify sqlite3 code, but you need to write y

Re: [sqlite] BACK API Questions

2009-12-15 Thread Raghavendra Thodime
Database Subject: Re: [sqlite] BACK API Questions > You don't need to modify sqlite3 code, but you need to write your own > code inside your application to do what you want. The sqlite backup > API, from what I understand, is not designed to solve the problem you > are try

Re: [sqlite] BACK API Questions

2009-12-15 Thread Raghavendra Thodime
-Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of P Kishor Sent: Tuesday, December 15, 2009 2:48 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] BACK API Questions On Tue, Dec 15, 2009 at 2:44 PM

Re: [sqlite] BACK API Questions

2009-12-15 Thread P Kishor
.org] On Behalf Of Martin.Engelschalk > Sent: Tuesday, December 15, 2009 12:17 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] BACK API Questions > > Hello Raghu, > > it seems to mee that you misunderstand the backup api. This api does not > "know&qu

Re: [sqlite] BACK API Questions

2009-12-15 Thread Raghavendra Thodime
Database Subject: Re: [sqlite] BACK API Questions Hello Raghu, it seems to mee that you misunderstand the backup api. This api does not "know" or care for your schema and tables, but backups the database block for block. In this sense, the api does not know "old" contents a

Re: [sqlite] BACK API Questions

2009-12-15 Thread Martin.Engelschalk
Hello Raghu, it seems to mee that you misunderstand the backup api. This api does not "know" or care for your schema and tables, but backups the database block for block. In this sense, the api does not know "old" contents and can not add "new" content. The backup api can not help you in your

[sqlite] BACK API Questions

2009-12-15 Thread Raghavendra Thodime
Hi, I am using in-memory db where I will execute only inserts. Periodically, I am trying to backup my in-memory db to file based db. But as soon as I backup, I want to clear up the in-memory db so that I will have enough memory for subsequent inserts. So next time when I back up I want to