From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Amit V Shah <ashah(at)tagaudit(dot)com> |
Cc: | "'pgsql-performance(at)postgresql(dot)org'" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Need help to decide Mysql vs Postgres |
Date: | 2005-05-24 17:14:35 |
Message-ID: | 429360FB.1040106@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
>
> I am not trying to start a mysql vs postgres war so please dont
> misunderstand me .... I tried to look around for mysql vs postgres articles,
> but most of them said mysql is better in speed. However those articles were
> very old so I dont know about recent stage. Please comment !!!
It is my experience that MySQL is faster under smaller load scenarios.
Say 5 - 10 connections only doing simple SELECTS. E.g; a dymanic website.
It is also my experience that PostgreSQL is faster and more stable under
consistent and heavy load. I have customers you regularly are using up
to 500 connections.
Note that alot of this depends on how your database is designed. Foreign
keys slow things down.
I think it would be important for you to look at your overall goal of
migration. MySQL is really not a bad product "IF" you are willing to
work within its limitations.
PostgreSQL is a real RDMS, it is like Oracle or DB2 and comes with a
comparable feature set. Only you can decide if that is what you need.
Sincerely,
Joshua D. Drake
Command Prompt, Inc.
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Amit V Shah | 2005-05-24 17:22:08 | Re: Need help to decide Mysql vs Postgres |
Previous Message | Amit V Shah | 2005-05-24 17:05:53 | Need help to decide Mysql vs Postgres |