>
> 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 hav
lite.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
> wrote:
>
From: 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 wrote:
> I
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 expected? Or Is
> ther
-
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 wr
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
> ar
> 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 trying to solve.
> == Kirshor-- I still don't get it. How can you copy
-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
f 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" or car
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" or care for your schema and tables, but backups the database
block for block. In this sense, the api does not know "old"
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 n
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 ba
12 matches
Mail list logo
