[MTOS-dev] Performance

Darin derwood at naebunny.net
Mon Mar 3 01:09:12 PST 2008


 > Hirotaka Ogawa wrote:

> Very informative!

> I think, adding a new published entry is a relatively large
> transaction.  I'd like to know analysis for more minute operations if
> you can.


I can tell you that this is not just limited to new posts.  Posting a 
comment uses up a similar amount of SQL queries.  I won't even go into a 
full rebuild.
Performance from 4.01 to 4.1 worsened significantly.  I posted a bug 
report a couple of weeks ago, and discussed it a bit with Chris Hall at 
SixApart. 
As a test, I enabled MySQL transaction logging on my server and created 
a log file of the SQL used to post a single comment to my wife's blog.  
I emailed the log to Chris in the hope that someone could see that there 
is a logic problem somewhere causing this explosion of SQL statements.  
The log file generated was 627 KB and over 10000 lines long.  Just for 
posting a single comment.

Doing a full rebuild of her blog takes approximately 12 hours. Now, 
while I don't have her blog on the fastest servers in the world, that is 
a significant departure from 3.xx and 4.01.  Rebuilds used to take about 
15 minutes on the same hardware.  Thats what I'd expect with 2100 
entries and 10000 comments. 

I've completely wiped out all remnants of past versions of MT, and I 
even created a blank database and populated it fresh after exporting via 
the export function so that there would be no old left-over tables or 
cruft from past MT upgrades.

The only thing I've been able to do to improve performance is to install 
memcached and set aside about 500 megs of memory for it to use.  That 
has helped some, but I don't see it as a true fix.  I've even considered 
switching from MyISAM tables to the Memory Storage Engine.

Darin -


More information about the MTOS-dev mailing list