On Sunday 26 February 2006 19:57, Ken Rickard wrote:

Thanks, that's a great list. My problem (which I had to explain to Karoly) is that I'm not a sysadmin, so I can't implement (or even really explain) these points.

That's another concern. Most of what Ben listed, while great advice, requires a dedicated server. How well does Drupal scale (number of users or number of nodes) for cases when you're on a shared host, and so don't have access to opcaches, db replication, etc? How can one squeeze the most performance out of a shared hosting environment? I don't know the answer that that, personally, but if someone does, please point me to the handbook page (or write one if it doesn't exist). -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson

On 27 Feb 2006, at 01:57, Ken Rickard wrote:

As I said to Karoly privately, part of our problem is that I _fell_ confident that Drupal will scale, I just don't have the tech cred to back that up.

So your list really helps.

There's a stub in the documentation where we hope to add some case studies of how well Drupal scales Performance Case Studies: Big Drupal sites http://drupal.org/node/44740 Two things we need in that section are some well known brands and some impressive metrics. I'll also direct your attention to: Drupal for professional consultants: an overview of typical client requirements http://drupal.org/node/43438 Which apart from bundling up info for consultants into one neat list, has also helped us identify some gaps in the documentation. Best regards, Robert Castelo Cortext Communications http://www.cortextcommunications.com