Keep in mind, though, that it's a MySQL hog. So you may find it sluggish if you're not on a VPS or (ideally) a dedicated server. But if you have 10k articles you're probably way beyond shared servers already. =)

Perhaps the thing I like best about Drupal -- other than the simplicity for a non-programmer like me and the large community of users -- is the Taxonomy system which will REALLY help you categorize your articles in a way that makes it easy for users to find the stuff they care about.

Plus the latest (dev) release of the Ad module *finally* lets users manage affiliate ads (Commission Junction, Amazon) in a powerful way. *drool*

drupal is not an option ... I heard a lot about it ... and this is site with 22000 unique visitors per day ... and almost 10.000.000 hits/day ... and drupal is in those conditions same as joomla ..

what do you think abour expression engine?

you mean like Mtv.com, New Yorker, Lifetime, Fox etc? All are using drupal. Search for "High Profile Drupal Sites"

I am sure they are many other options, just thought to comment on that.

The first two are very high-volume sites but have mostly anonymous visitors - and Drupal does a great job of serving cached pages to anonymous visitors. The third is a community site so most users are logged-in, which is a more difficult problem, but they've also done a really good job optimizing for their large number of users.

Large volume sites can definitely be done on Drupal. Doesn't even really need a super-powerful server, it just likes dedicated hosting in order to be snappy. (My "sluggish" complaint was really just about shared servers. And it's definitely no worse than, say, MediaWiki ... but don't get me started on that bag of frowns!)

That said, something custom will obviously be more customizable for performance. But it'll cost you more time and money and thought to set up and maintain.

Best of luck to you!

That alone doesn't mean much. They could have a the database clustered and a server farm for the front end. Without knowing the architecture it doesn't say much about scalability or lack of scalability, just that some house hold names use the product.

As to the OP if you have that many articles and high traffic site, a cms that is capable of spitting out static files may help you. Now if each of those articles is heavily tailored to the user requesting them, then you are pretty much stuck puttting things together on the fly, but if it's not personalized content, it's hard to beat plain old static files for performance.

There is a site that compares CMS's side by side so you can see the features etc. I don't think I can post a link here though so PM me if you want or if it is ok to at least say what to search for I'll edit the post at a later time.

[edited by: CrustyAdmin at 5:47 am (utc) on Jan. 23, 2008]

Drupal also has cache (from 1 min to hours) that serve info in a flash. By trying several cms he loses nothing