Scalability for Thousands of Posts

Deane, the version you’re running will greatly effect the render time. Send me an email (m at this domain) and I may be able to help you out more if you can send me a dump of your database. There’s no reason any page (except the ridiculously large ones) should take more than a second to render.

I’m running the latest version — I just downloaded it earlier today.
I have emailed you a database dump.
Deane

Latest nightly build? Or latest official release? If you’ve already told Matt, then nevermind. ??

Latest official release: 1.01

If I recall, a static page option WAS in the works at some point…

Another thing a caching option would provide would be the ability to render different archives with different templates. For instance, category pages could have one template, individual pages could have another, etc.
I’ve been playing around a bit with Smarty and WordPress. It seems quite feasible.
Deane

@antifuse: really? which versionw as that?

Deane, I agree that is way too many queries… I’ve got a hack I haven’t released yet that caches the home page. Contact me directly if you are interested. Still need to solve the too many queries problem though.

2.759 seconds….. for the number of posts on the page, that isn’t too shabby.
As for static versions of the pages, allusion will have the final word on that, but AFAIK there isn’t any plans. That’s why the data is in a DB. The reason being that the pages would have to be rebuilt each time there is a post…. and with posts having the ability to go into multiple categories, and sub categories…. the page building to be intense.
Caching the main page….. hmmmm…… will have to think about that, but I’m not all too sure that’s a viable option…. but it would depend on the implementation and other options available.
TG

I swear I recall somebody saying they were working on a static page hack… but I am way too lazy to go back looking through the forums for it… hehehehe…

Another (less expensive) enterprise CMS, CrownPeak Advantage, has a similar model (WORM.) Everything is stored in the database, and they keep a changelog (record of delta’s). When a page is updated, added, or removed…that page and any that it affects are pushed back out as static pages. It works great and is very scaleable.
Of course, I use WP for blogging, not enterprise content management…I do see the benefits, though, of writing pages out statically until they change…posted to the permalink directory structure.
-Tony

“Of course, I use WP for blogging, not enterprise content management…”

I do want to clarify that I’m not digging on WP in this thread or anything. I just really need to know the limits of its scalability.
Based on my tests, it will not scale to the volume we have. I just can’t have 10 second page gen times and hundreds of database queries per page.
It could very well be that we’re looking for WP to do something it’s not meant to do. I just wanted to confirm that I hadn’t hosed the install or the config or something.
Does anyone know what the largest current WP install is, in terms of posts, comments, and categories? I’d be interested to know.
Deane

Deane, there is a great deal of benefit to caching content. Because it isn’t in the current release of WordPress doesn’t mean the developers don’t realize those benefits. It’s all a matter of priorities.
How fast is your server? I have ~800 posts and ~1000 comments and my average load time for a category page (12 posts I think) is under 1 second. Like I said, my blog home page is cached so it spits out in ~.03 seconds.

For the record, I moved servers and page gen times dropped dramatically — less than a second in most cases. It was on a server shared by 200 other sites. The new server has barely any traffic.

Deane: Seems the queries have really dropped, too.