Previous Message
Next Message

High Volume Open Source CMS Sites

Sent by Hauck, William B. on 13 January 2004 19:07


Derrick,

Just curious about 4-5 MB files.  I can understand serving up millions
of them daily, but would you really be uploading 1000 4-5MB files
daily?!  What type of site are you thinking of?  A news site with _lots_
of video clips?

Aside from serving these files, you'd have to have quite the
infrastructure to support storing them ... adding 4GB daily would take
lots of disk space, bandwidth, etc.  Would it even be advisable to host
all this content in a single CMS?  Wouldn't it be better to use a
service like Akami to spread the load around, give shorter paths to the
data, and be disaster-tolerant?

Again, just curious.

Thanks,

bill

-----Original Message-----
From: Derrick Oien [EMAIL-REMOVED]] 
Sent: Thursday, January 08, 2004 1:54 PM
To: Rob Page; [EMAIL-REMOVED]
Subject: RE: [cms-list] High Volume Open Source CMS Sites


When I was thinking about high volume the parameters I was thinking
about 
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 
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.

-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 
>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.


CONFIDENTIALITY NOTICE: This E-Mail is intended only 
for the use of the individual or entity to which it is addressed and may contain information that is
privileged, confidential and exempt from disclosure under applicable law. If you have received this
communication in error, please do not distribute and delete the original message.  Please notify the
sender by E-Mail at the address shown. Thank you for your compliance.


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

Possibly related: