Re: Probable faq: need some benchmarks of pgsql vr.s mysql
- From: Brian Hurt <bhurt(at)spnz(dot)org>
- To: Josh Berkus <josh(at)agliodbs(dot)com>
- Cc: pgsql-advocacy(at)postgresql(dot)org
- Subject: Re: Probable faq: need some benchmarks of pgsql vr.s mysql
- Date: Fri, 29 Oct 2010 17:37:19 -0400 (EDT)
- Message-id: <alpine.DEB.2.00.1010291732020.31170@sergyar> <text/plain>
For the record, the table we're having trouble inserting into is ~100 rows
with ~50 indexes on it. E.F Codd is spinning in his grave. The reason
they went with this design (instead of one that has two tables, each with
3-6 columns, and about that many indexes) is that "joins are slow".
Which they may be on Mysql, I don't know. But this is (unfortunately) a
different battle.
Brian
On Fri, 29 Oct 2010, Josh Berkus wrote:
Brian,
Rob pointed me to a benchmark of MySQL vs. Tokutek which is interesting
to your case:
http://www.mysqlperformanceblog.com/2009/04/28/detailed-review-of-tokutek-storage-engine/
It's also interesting to me because apparently InnoDB *does* have an
issue with large numbers of inserts to an already-large table, which we
don't have (I don't think we do, anyway).
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
--
Sent via pgsql-advocacy mailing list (pgsql-advocacy(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy
Home |
Main Index |
Thread Index