It could be that there is no transaction block wrapped around the inserts (a
BEGIN TRANSACTION before the start of the insert loop, and a COMMIT
TRANSACTION at the end.)  If there is no explicit transaction, then every
insert has an implied transaction, which considerably slows down the
database engine.

Ian

On 1/18/07, Gaurav Arora <[EMAIL PROTECTED]> wrote:

Hi All,
I am a newbie to SQlite, just saw that the performance numbers on
www.sqlite.org are not reliable (as per the notce on website,
http://www.sqlite.org/speed.html <blocked::
http://www.sqlite.org/speed.html>
)
So, I thought of profiling SQlite operations, on linux platform
the performance time is quite good.
I build sqlite on Windows too, and saw discouraging numbers coming out of
it, following are some of them.
e.g.
RH9:
inserting 1000 records ~.07 seconds.

WindowsXP:
inserting 100 records ~11 seconds.
inserting 1000 records ~113 seconds.

May be I did something wrong for building, or the parameters passed for
building sqlite werent correct.
I am willing to update the test results on the site, could anyone here
guide
me for the things which I might be doing wrong.

Thanks in advance.
//Gaurav


Reply via email to