Given Johns suggestion of faster disk:
   a 15k disk should get 125 commits /second.
   a  10k disk should get 83 commits/ second
   a 7200 gets 60 commits/second

I wonder what the impact of the varying filesystem configurations would have on 
sqlite commit performance ?
Say reiser, ext3 (journaled/ordered), etc..

Maybe you have different filesystems. What about raid devices?

Ken


Fabio Durieux Lopes <[EMAIL PROTECTED]> wrote:  Hmm, GW0 (RHE3, the fast one) 
does 190-300 inserts/second. GW2 does 
around 15 inserts/second.

 I'm gonna try to commit every 1000 records and I'll be back with 
results.

 Thanks!

On 26 Oct 2007 at 17:02, [EMAIL PROTECTED] wrote:

> "Fabio Durieux Lopes"  wrote:
> > 
> > I've seen people saying one should use transactions....
> > [B]ut my question is: If I'm using the same binary on 
> > both computers shouldn't I get similar performances on
> > both computers?
> > 
> 
> INSERT is very fast in SQLite.  What is slow is not
> the INSERT but the implied COMMIT that occurs after
> each INSERT if you do not have an explicit transaction.
> The COMMIT does not return until all data has been
> safely written to the disk platter.  This typically
> takes two complete rotations of the disk platter, which
> means you can do no more than about 60 COMMITs per
> second on your average computer.  In contrast, you
> should be able to do 60000 INSERTs/second.
> 
> SQLite uses the fsync() system call to make sure
> data has reached the disk before continuing.  But
> fsync() is busted on some implementations.  On 
> some systems, fsync() is a no-op.  This certainly
> makes it run a lot faster, but the downside is that
> the data does not necessarly reach the disk surface
> when SQLite thinks it does, and so if you lose power,
> your data might get corrupted.
> 
> I have not heard of problems with fsync() on RHE3.
> But perhaps fsync() is disabled on that OS.  Or 
> perhaps fsync() is disabled by the particular disk 
> controller you are using.  Who knows.
> 
> This is certain:  By the laws of physics you cannot
> do more than about 60 transactions per second on a
> 7200 RPM disk drive.  If you are seeing more than
> that, then something is wrong with your system and
> you will likely corrupt your databases if you lose
> power.
> 
> --
> D. Richard Hipp 
> 
> 
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -----------------------------------------------------------------------------
> 


--
Fabio Durieux Lopes
Desenvolvimento
Suntech Telecom Solutions
www.suntech.com.br
Office: +55 48 3234 0107

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------


Reply via email to