RE: High Volume Open Source CMS Sites

Or, don't even use the CMS for publishing.  The CMS should be used for
managing content (Create/Workflow/Version).  The database or file server =
for
storage.  And your preferred application servers and Web scripting =
languages
for publishing.

CMS scalability problem solved & eliminated!

Graham

________________________=20
J Graham Zahoruiko=20
President & CEO=20
Refresh Software Corporation=20
51 Middlesex Street=20
North Chelmsford, MA  01863=20

P: 978-251-8870 x221=20
F: 978-251-8872=20

www.refreshsoftware.com=20

SiteRefresh - Core Content Management=20
Free Online Trial & Developers Sandbox=20

-----Original Message-----
From: cms-list-admin-/[email protected] [mailto:[email protected]] =
On
Behalf Of Derrick Oien
Sent: Thursday, January 08, 2004 1:54 PM
To: Rob Page; cms-list-/[email protected]
Subject: RE: [cms-list] High Volume Open Source CMS Sites


When I was thinking about high volume the parameters I was thinking =
about=20
generally were:

3-5 million pageviews per day with multiple assets per page.

Serving 3-4 million 4-5 megabyte files per day.

Ingesting into the content management system approximately 1000 4-5=20
megabyte files per day.

My experience was with a top 1000 website and dealing with a CMS that we =

made from scratch, my hope is that the open source solutions have this =
sort=20
of scalability today assuming the right combinations of hardware, etc.

-Derrick



At 09:45 AM 1/8/2004, Rob Page wrote:
>On Thu, 2004-01-08 at 02:24, Grant Malcolm wrote:
> > Curious to know what might be defined as high volume?
><snip>
>
>I think this is an excellent question and one that crosses the open=20
>source and proprietary boundary.
>
>In our experience, there are at least eight scale variables:
>
>  - total size of the managed corpus
>
>  - percentage of the total corpus that's "in play" at any given time
>
>  - retail hits per second
>
>  - content (e.g., page, page fragment, and "object") cache-ability
>
>  - aggregate outbound bandwidth for non-streaming content
>
>  - aggregate outbound bandwidth for streaming content
>
>  - content editor/author/management hits per second
>
>  - system-generated events- or "hits-" per second
>      (auto keywording, feeds management, etc.)
>
>  - user interface scaling (this is hard to define but important)
>
>Others?
>
>--
>Rob Page                V: 540.361.1710
>Zope Corporation        F: 703.995.0412
>
>--
>http://cms-list.org/
>please trim your posts.


--
http://cms-list.org/
please trim your posts.

--
http://cms-list.org/
please trim your posts.