[wp-hackers] OT: MySQL optimization
chris at clwill.com
Tue May 8 15:26:38 GMT 2007
Did it yesterday, took only about 15 minutes to do the conversion.
Read performance seems comparable or slightly better. Interestingly, write
performance is much improved.
The one "gotcha" is that the database is now 9gb... a 50% increase in size.
> From: Aubrey Kilian <aubreykilian at gmail.com>
> Subject: Re: [wp-hackers] OT: MySQL optimization
> You might want to schedule some downtime before changing. :-)
> Converting 6.5GB of myisam table into innodb might take a while.
> But then, naturally one would assume that you'd be trying this on a
> development machine with a copy of the live database first, right?
> And it'd be a good idea to see the pros and cons of innodb vs. myisam
> tables, amongst others, as Matt pointed out, is performance increase
> on heavilly indexed tables, and transactions support, but there's a
> bit of a performance hit for reading, and you lose fulltext indexes.
> It'd be worth doing benchmarks on your specific instance me thinks.
More information about the wp-hackers