When I was thinking about high volume the parameters I was thinking about
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
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
of scalability today assuming the right combinations of hardware, etc.
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?
>I think this is an excellent question and one that crosses the open
>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)
>Rob Page V: 540.361.1710
>Zope Corporation F: 703.995.0412
>please trim your posts.
please trim your posts.