*** 55,57 **** --- 55,87 ---- ---- _E. Russel Harvey on 2004-09-25:_ Does a transaction caused file locking prevent not only writing but also reading from other access, which may be from a thread of the same process that SQLLite is running? + + + ---- + + **Database size and performance** + + _Charles Thayer on 2005-02-17:_ + + I tried some small tests to see if sqlite3 would do a decent + job for a project. + + I found that inserts into a single table with + a few indices scaled well. At first I was able to + do 72 inserts/sec, and that number went down linearly for a while + but then stopped degrading. + After 8 million rows (1.6GB), I was still inserting at about 34 rows/sec. + + With the same schema, I did a select test which does a "select count(*)" + and then "select count(*),somecolumn from sometable group by somecolumn". + (There was an index on somecolumn). + In this case I found that the queries took around 2 seconds per 100,000 + rows, and scaled linearly with db size. + + Environment: + *: Linux 2.4.22, sqlite 3.0.8 + *: ext2 on IDE drives + *: Dual Pentium 4 @ 2.6GHz + *: 1GB RAM + + ----
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|