|
Home > Archive > Microsoft Content Management Server > December 2005 > Pushing the bounds of CMS2002 Enterprise
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Pushing the bounds of CMS2002 Enterprise
|
|
| Paul Devenney 2005-12-16, 5:54 pm |
| Hi folks,
does anyone have any experience/calculators on the performance bounds of CMS
2002? How many sites can realistically be run off a single server running
enterprise edition (SQL on a different machine)? Where are the limiting
factors (memory/processor or both).
Given a hardware spec, how can I realistically calculate the total number of
sites/total pages that a CMS server can cope with.
any advice/experience is greatfully accepted.
Cheers,
Paul
| |
| Stefan [MSFT] 2005-12-16, 5:54 pm |
| Hi Paul,
this question cannot be answered in general as it depends on the load of
each site and also on the coding.
You need to evaluate this for each site individually.
The following whitepaper will help you to get an answer for your specific
setup:
http://www.microsoft.com/downloads/...&DisplayLang=en
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Paul Devenney" <spam@spamgohere.com> wrote in message
news:O8ldXqlAGHA.3436@TK2MSFTNGP10.phx.gbl...
> Hi folks,
>
> does anyone have any experience/calculators on the performance bounds of
> CMS 2002? How many sites can realistically be run off a single server
> running enterprise edition (SQL on a different machine)? Where are the
> limiting factors (memory/processor or both).
>
> Given a hardware spec, how can I realistically calculate the total number
> of sites/total pages that a CMS server can cope with.
>
> any advice/experience is greatfully accepted.
>
> Cheers,
>
> Paul
>
| |
| Rovastar 2005-12-19, 5:55 pm |
| That is very true Stefan however often a few a few hints can be used to
indicate it might be a problem.
Excessively big sites can be problematic.
I don't know if you have CMS already and you are analysing the environment
(like I am atm) or if you are just investigating if CMS would be a good
switch.
CMS is intensive and if you compare pure static content it has much more of
an overhead.
CPU and memory are both used heavily but like any site it has depends on the
site.
Separate SQL is the first big benefit really. Things get especially
complicated if you make it an MSIB suite and include Commerce Server so
consider this when you specing out.
There can be problems if a channel is too big like over 10,000 postings and
it does not export them!  apparently CMS SP2 could fix some of these issues
but I am not brave enough to install that in our webfarm just yet. ;)
But if you have CMS already...
Running a query for the amount of nodes is a good start if you already have
the CMS server up and running (Run on your CMS database):
SELECT count(*) FROM node
WHERE (datediff(hour, archivedwhen, getdate()) < 1
OR archivedwhen IS null)
AND (deletedwhen is NULL)
AND datediff(hour, expirydate, getdate()) < 1
AND (datediff(hour, effectivedate, getdate()) > 1
OR effectivedate IS null)
AND (datediff(hour, approvedwhen, getdate()) > 1
OR (type >= 65535 and approvedwhen is null))
Microsoft recommend for this query 35,000 'nodes' although you can have more
if that are not to processor intensive and decent hardware.
Also there are other tools to use like the must have MCMS Manager:
http://mcmsmanager.sourceforge.net/
There are health check tools in there to give you indications. The app is
updated regularly too. (Last time a few of weeks ago)
Hope it helps
John
--
http://www.milkdrop.co.uk
http://r4.rabidhamster.org
"Stefan [MSFT]" wrote:
> Hi Paul,
>
> this question cannot be answered in general as it depends on the load of
> each site and also on the coding.
> You need to evaluate this for each site individually.
>
> The following whitepaper will help you to get an answer for your specific
> setup:
> http://www.microsoft.com/downloads/...&DisplayLang=en
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> Check out the new book as well: Advanced MCMS development:
> http://tinyurl.com/8ugwj
> ----------------------
>
>
> "Paul Devenney" <spam@spamgohere.com> wrote in message
> news:O8ldXqlAGHA.3436@TK2MSFTNGP10.phx.gbl...
>
>
>
| |
| Stefan [MSFT] 2005-12-20, 2:49 am |
| Hi,
just to add: for the SQL query: we have customers who have more than 30
million nodes here with good performance as node caching is only one flavor.
Much more important is a good implementation of ASP.NET output caching.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Rovastar" <Rovastar@..*hotmail*...c.o.m> wrote in message
news:60C57512-6306-41C5-9589-2C30A9C91912@microsoft.com...[vbcol=seagreen]
> That is very true Stefan however often a few a few hints can be used to
> indicate it might be a problem.
>
> Excessively big sites can be problematic.
>
> I don't know if you have CMS already and you are analysing the environment
> (like I am atm) or if you are just investigating if CMS would be a good
> switch.
>
> CMS is intensive and if you compare pure static content it has much more
> of
> an overhead.
>
> CPU and memory are both used heavily but like any site it has depends on
> the
> site.
>
> Separate SQL is the first big benefit really. Things get especially
> complicated if you make it an MSIB suite and include Commerce Server so
> consider this when you specing out.
>
> There can be problems if a channel is too big like over 10,000 postings
> and
> it does not export them! apparently CMS SP2 could fix some of these
> issues
> but I am not brave enough to install that in our webfarm just yet. ;)
>
> But if you have CMS already...
>
> Running a query for the amount of nodes is a good start if you already
> have
> the CMS server up and running (Run on your CMS database):
>
> SELECT count(*) FROM node
> WHERE (datediff(hour, archivedwhen, getdate()) < 1
> OR archivedwhen IS null)
> AND (deletedwhen is NULL)
> AND datediff(hour, expirydate, getdate()) < 1
> AND (datediff(hour, effectivedate, getdate()) > 1
> OR effectivedate IS null)
> AND (datediff(hour, approvedwhen, getdate()) > 1
> OR (type >= 65535 and approvedwhen is null))
>
> Microsoft recommend for this query 35,000 'nodes' although you can have
> more
> if that are not to processor intensive and decent hardware.
>
> Also there are other tools to use like the must have MCMS Manager:
> http://mcmsmanager.sourceforge.net/
>
> There are health check tools in there to give you indications. The app is
> updated regularly too. (Last time a few of weeks ago)
>
> Hope it helps
>
> John
>
> --
> http://www.milkdrop.co.uk
> http://r4.rabidhamster.org
>
>
> "Stefan [MSFT]" wrote:
>
| |
| Paul Devenney 2005-12-20, 7:59 am |
| ASP.NET caching is indeed one of the things we will look at.
Basically we are trying to assess how many sites can be hosted off a given
SQL server/Webserver combo. I will certainly look at the information
provided. Thank you very much! I'll let you know if i come to any particular
conclusions
cheers,
Paul
"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:ec2c3CUBGHA.3164@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> just to add: for the SQL query: we have customers who have more than 30
> million nodes here with good performance as node caching is only one
> flavor. Much more important is a good implementation of ASP.NET output
> caching.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS:
> http://tinyurl.com/6zj44
> Check out the new book as well: Advanced MCMS development:
> http://tinyurl.com/8ugwj
> ----------------------
>
>
> "Rovastar" <Rovastar@..*hotmail*...c.o.m> wrote in message
> news:60C57512-6306-41C5-9589-2C30A9C91912@microsoft.com...
>
>
| |
| Mike Sharp 2005-12-21, 8:49 pm |
| This isn't much of a data point, but I was recently running Application
Center Test against our web farm (consisting of 2 decent sized servers, with
a separate SQL cluster). The maximum load I could dish out from the
workstation running the test was about 24,000 pages per hour (limited by the
workstation, or it's network connection I'm sure). Even then, when
requesting pages from a different workstation, the site was quite
responsive. We have a pretty good caching strategy, though, and during the
test you couldn't even notice the activity on the SQL cluster. The pages on
our site are computationally fairly heavy, IMO, and the code isn't the most
efficient.
Regards,
Mike Sharp
"Paul Devenney" <spam@spamgohere.com> wrote in message
news:%23tSNKWVBGHA.1032@TK2MSFTNGP11.phx.gbl...
> ASP.NET caching is indeed one of the things we will look at.
>
> Basically we are trying to assess how many sites can be hosted off a given
> SQL server/Webserver combo. I will certainly look at the information
> provided. Thank you very much! I'll let you know if i come to any
particular
> conclusions
>
> cheers,
>
> Paul
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:ec2c3CUBGHA.3164@TK2MSFTNGP10.phx.gbl...
rights[vbcol=seagreen]
more[vbcol=seagreen]
on[vbcol=seagreen]
is[vbcol=seagreen]
of[vbcol=seagreen]
http://www.microsoft.com/downloads/...&DisplayLang=en[vbcol=seagreen]
bounds[vbcol=seagreen]
server[vbcol=seagreen]
the[vbcol=seagreen]
>
>
|
|
|
|
|