[MTOS-dev] InnoDB performance

[Alvar Freude]

-- Bud Gibson <fpgibson at gmail.com> wrote:

> Isn't MyISAM the default?  As I recall from past experience, I thought
> InnoDB's main strength was transaction processing.

InnoDB is usually faster then MyISAM; also with simple read queries. And 
both are usually slower then PostgreSQL.

The mentioned InnoDB performance problem was a bug in MySQL and is fixed.


> It would seem blog
> performance is really more bound by query processing.  So, I'd be
> surprised to hear a lot of blog installs were using InnoDB, but that is
> probably just my academic perspective.

With MyISAM it is not possible, to enforce data integrity and it has a 
lot of trouble with concurrent write or read/write statements and it is 
not easy to create a consistent backup without downtime and so on. So, I 
see no reason to use MyISAM.

And, generally spoken, not with Movable Type in mind: if one can choose, 
it is almost every time better to take PostgreSQL: it has a lot more 
features, is more stable, has fewer stupid gotchas and is faster then 
MySQL.


Or in other words: there are no performance reasons to do not support 
transactions and data integrity features. Data integrity (and for this: 
transactions) is a very basic and important thing for storing data and 
poorly Movable Type lacks in this aspect. e.g. when the webserver crashes 
while MT writes something to the database, the database may become broken.


Ciao
  Alvar


-- 
** Alvar C.H. Freude, http://alvar.a-blast.org/
** http://www.assoziations-blaster.de/
** http://www.wen-waehlen.de/
** http://odem.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://www.sixapart.com/pipermail/mtos-dev/attachments/20080308/b6014da9/attachment.bin