I’m currently working on a wordpress mu project which is making me pull out me already shot hair. Rasmus from Verk and I have discussed the issues, his argument was that Drupal would be faster out of the box, I still haven’t done me first Drupal project yet, but it looks promising.
Based on Wim Mostreys entry regaring the database architecture of wordpress mu, he claims that Drupal is faster than wordpress mu and that the number of tables created per user is an issues. I kind of disagree with him.
Imagine having a blog community containing 10000 blogs with a couple of 100 posts per blog all stored in the same table in your database. Now, if I want to run queries on all blogs to get a list of the most resent posts, one big table would be the fastest solution agreed.
But what if you only have to serve the content of a single blog?
Lets say you only have to handle my entries and the remaining 9999 (I know I’m not much of a blogger), running that query on just one table in the database can in no way be any slower than the first option.
So, although the database architecture behind wordpress mu may look disturbing, it’s actually not that bad.
Filed under: Blogroll , wordpress mu
