Here is a very interesting thread started today in the TextDrive Forums: Who’s Biggest Shared Hosting Resource Hog: WP or MT?
Doubtless due to having too much time on my hands, I’ve built two visually identical versions of a new blog that will be eventually hosted here. One version is in WordPress, the other is in Movable Type.
Personally, I don’t have any real preference for either WP or MT. But, I do have a bias for static pages, because I think (imagine?) that they’re delivered faster from a reader’s point of view. Subjectively speaking, static sites feel snappier to me than a lot of WP sites.
Hence, I’ve got two questions:
1) Side by side, on the same machine with the same browser, would Jill Reader really see a static page produced by MT before she’d see the identical page delivered by WP?
2) Which of the two platforms is most likely to run afoul of CPU/memory/etc. limits imposed by shared hosting? I know this really isn’t an issue for the typical blog with minimal readership, but let’s dream. Suppose a site does become popular. WP is going to be busy generating a lot of database queries. MT is going to be busy rebuilding some number of pages pages every time someone posts a comment. (MT won’t rebuild the entire site on its own.) I’m assuming the sites have identical content, the same posting rate, same comments, etc.
(There are plenty of complaints on the web from MT users who’ve run into problems obviously caused by excessive resource use on a shared host. But, if you look, there are also complaints from WP users who’ve run into problems.)
I’ve left comment spam out of the equation because I suspect both platforms are equally vulnerable. Akismet and other equivalent spam countermeasures are avaiable [sic] for both.
I’m shooting in the dark here, but I’m guessing that the key variable might be the comments. I.e., with few comments the edge might go to MT, but as comments increase, the rebuilds will suck more resources than the corresponding database activity will with WP.
Has anyone ever run some numbers on this?
I would love to see some great discussion around this. Will Jason weigh in? My gut tells me the Perl/CGI structure of Movable Type is the bigger resource drain, but I could be wrong.
Recent Comments