BLACK FRIDAY Sale with 50% off starts in: 
SQLite Database which one is the fastest?
January 5, 2005 by Frank Beverdam Source article

The race is on at where they conduct a series of speed tests for Linux databses using SQLite 2.7.6, PostgreSQL 7.1.3, and MySQL 3.23.41.

SQLite finish first, MySQL is the runner up, with PostgreSQL trailing the pack.

Note to Access users: MySQL can do 25,000 inserts in two seconds. SQLite can do it in less than one second. While Access is great for desktop work, I shudder to think how it would stack up in this test.

A summary of the test;

  • SQLite 2.7.6 is significantly faster (sometimes as much as 10 or 20 times faster) than the default PostgreSQL 7.1.3 installation on RedHat 7.2 for most common operations.

  • SQLite 2.7.6 is often faster (sometimes more than twice as fast) than MySQL 3.23.41 for most common operations.

  • SQLite does not execute CREATE INDEX or DROP TABLE as fast as the other databases. But this is not seen as a problem because those are infrequent operations.

  • SQLite works best if you group multiple operations together into a single transaction.

The results presented here come with the following caveats:

  • These tests did not attempt to measure multi-user performance or optimization of complex queries involving multiple joins and subqueries.

  • These tests are on a relatively small (approximately 14 megabyte) database. They do not measure how well the database engines scale to larger problems.

Place your comment about SQLite Database which one is the fastest?

You must me logged in to write a comment
Database Speed
January 6, 2005 by Kev Brown

Ok - first off, look who's displaying the article. SQLite. Second of all, nice that they compare the most recent version of SQLite with an older version of Postgres.

Third, and most importantly, you're comparing apples and oranges here - it's like comparing Access to Oracle. Sure SQLite is faster than PostgreSQL, but it doesn't support a multitude of features or complience factors that PostgreSQL does. Users, Groups, Schemas, Tablespaces and permissions to name but a few. I think that this benchmark set would be much more valid if they gave examples of applications where this would be used.

I'm currently in the process of implementing SQLite for my website - purely for data presentation. As a data storage method it is severely lacking and nowhere near strong enough to sun any type of aapplication off. PostgreSQL is a database, SQLite is a dat file interpreter/SQL interface, let's not dress it up any more than that. To call it a database is a bit of a stretch.

Just thought I'd chip that in.