More than a year ago I worked with Wordpress in a content-aggregator setup… this means we had about 20-100 new posts per day.
At that time I found a lot of really performance hog SQL queries in the wordpress installation 1.2 and later 1.5
to finish my follow up for the last years post – I got a wordpress installation with 100,000 posts to run by the following actions
Domas wrote about similar troubes and issues with the MYSQ queries
I had inner voice inside (from the hosting business past) – but MySQL has query cache! Yes, it has, but putting timestamps into queries eliminates possibilities of caching. And one should not rely on query caching, one should rely on data and index caching. This is where databases shine.
Final question: Will upgrade to WordPress 2.0 solve these issues? Won’t I be trapped in yet another featuritis?
My initial feeling that wordpress was not written for content aggregation can be confirmed.
Some links to other performance issues with wordpress tell us a lot:
Generally the advice is to install the WP-Cache module, which allows static caching of wordpress blogs… I wonder how if affects all those inperformant reverse index lookups and such…
However, today I revisit Wordpress 2.0 and wonder about improvements made on the performance side…
I will try that WP-Cache 2 module and see how an out-of-the-box Wordpress 2.0 installation handles 100,000 entries in a blog :-) From the first look this module will help A LOT... we will see.
Recent comments
1 day 20 hours ago
1 week 12 hours ago
1 week 2 days ago
10 weeks 1 day ago
10 weeks 1 day ago
10 weeks 3 days ago
10 weeks 4 days ago
11 weeks 3 days ago
19 weeks 1 min ago
21 weeks 1 day ago