Allan Edwards wrote:
If my instincts and research is correct, most other databases simply cache
the transactions in memory to give the appearance that they are inserting
very quickly, but the truth is they are probably not quite as safe as Sqlite
since it writes the data to disk immediately upon receipt. This appears to
be the bottleneck.
I think you are correct. If you think about how a disk driver works,
you'll quickly realize that to truly commit a transaction to the disk
surface requires at least one revolution of the platter. So for a
5400 RPM disk drive, you will get (at most) 90 transactions per second.
SQLite gets you very close to this number. The INSERT times reported
back by other database engines often exceed this number, which tells
me they are not really committing the changes to the disk surface before
they return.
I would be interested in knowing more about the internals of Sqlite that
make it perform without having to do a major study of the code. I have read
the architecture books on most other major databases, but not on Sqlite. : -
Allan: If you will call me (at the number below) and explain the
internals of other major database engines, I'll explain everything
you care to know about SQLite.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
