| From: | Erik Jones <ejones(at)engineyard(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Justifying a PG over MySQL approach to a project |
| Date: | 2009-12-17 09:41:54 |
| Message-ID: | 11317F2A-D9F6-4C6A-B48B-DFB62D1239CC@engineyard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 16, 2009, at 10:30 PM, Craig Ringer wrote:
> - If you don't care about your data, MySQL used with MyISAM is *crazy* fast for lots of small simple queries.
This one causes me no end of grief as too often it's simply touted as "MyISAM is fast(er)" while leaving of the bit about "for lots of small, simple queries". Developers then pick MySQL with MyISAM storage and then scratch their heads saying, "But! I heard it was faster...," when I tell them the reason their app is crawling is because they have even moderately complex reads or writes starving out the rest of their app thanks to the table locks required by MyISAM. As you mentioned, for the type of active workloads that MyISAM is good for, you might as well just use memcache over something more reliable and/or concurrent, or even a simple key-value or document store if you really don't need transactions.
Erik Jones, Database Administrator
Engine Yard
Support, Scalability, Reliability
866.518.9273 x 260
Location: US/Pacific
IRC: mage2k
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Jones | 2009-12-17 09:48:23 | Re: How to get text for a plpgsql variable from a file. |
| Previous Message | A. Kretschmer | 2009-12-17 09:38:32 | Re: flagging first row inserted for each "group" of key |