Do you train Kung Fu?
Or know someone who does?
Then check out KungFuPeople.com
Mobile version of this page
Save this page in del.icio.usChallenge Osama with scimitar or sword
Next:
XHTML, HTML and CSS compressor
Related blogs
PSP - Python Server PagesLoadtesting this site and compare with static Apache
Adding a year in PostgreSQL
Creating a user for postgresql
Fastest way to uniqify a list in Python
Gzip and Slimmer optimization anecdote
To $('#foo p') or to $('p', $('#foo'))
rfc822() vs. rfc1123_date()
Why bother with MySQL...
Speed test between django_mongokit and postgresql_psycopg2
Sorting transform function in PostgreSQL
Date formatting in Python or in PostgreSQL (part II)
Quick PostgreSQL optimization story
ALTER TABLE patch
Just Oracle and IBM?
List of casts in PostgreSQL
pg_class to check if table exists
Running simple SQL commands on the command line
Integer division in programming languages
Date formatting in python or in PostgreSQL
To sub-select or not sub-select in PostgreSQL
Related by category
PostgreSQL, MySQL or SQLite
http://www.hwaci.com/sw/sqlite/speed.htmlpostgresql, mysql, benchmark, pgsql, sqllite, benchmarking
4th of April 2004
I use PostgreSQL a lot but these benchmarking results surprise me. MySQL is often much faster than PostgreSQL and SQLLite is several times faster than MySQL.
What matters to me is how fast they work with Python, or in particular Zope. I need to make my own benchmark of MySQL and PostgreSQL with Zope and all the various database adapters.
The reason I moved from MySQL to PostgreSQL was partly because PostgreSQL has more enterprise features and that my colleges use PostgreSQL. But I suspect that for many of my projects I never even use these features.
Then I also found this from a Zope mailing list:
>The speed comparisions with PostgreSQL are very much an apples vs. fish
>sort of thing: the pgsql server was not tuned at all, and does a whole
>lot more that was never tested, such as multi-user writer access.
Comment
Try using the mysql 'innodb' engine instead of myisam.. you'll see a performance difference (see mysql.com for details on why they are different).
I should've added to the previous comment - this will compare properly to postgresql. comparing myisam tables to postgresql won't tell you anything - they are completely different.
the innodb engine on the other hand supports row level locking which means count(*) type queries can't use the table metadata (like a myisam table can).
The post is on target. For most projects, one should concentrate on the code more than the data persistance issues. For speed and convenience, SQLite takes the cake. To concentrate on Python code, one could for example use y_serial http://yserial.sourceforge.net which has an elegant interface for quick development.
I'd take that with as much seriousness as someone on a postgresql list talking about the speed of the ZODB...