Hi,

I have a question regarding a statement in the MCMS Faq.
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm#4009EC9B-3902-4625-93EB-B6F5777BDDF2

In the section "Is there a limitation for Postings per Channel?" it says
"Root Channel containers:
Limit the number of containers under the root node. (For example, /Channels
should not have more than 10 to 15 immediate children containers.) "

What impact does it have if there is more than 10 - 15 immediate childrens
of the Channels node?
Currently we have around 50 containers under the root channel node and
around the same amount of containers under the root ressourcegallery node.

Would it make any difference in terms of performacne to have a structure
like this

/Channels/OneChannelContainer/50ChannelContainers instead of
/Channels/50ChannelContainers

Is the issue only related to poor performance when using the Site Manager or
does it impact accessing the objects through asp.net?

Kind regards

Tony

[ Post a follow-up to this message ]

Hi Tony,

that is only a rule to let MCMS be a good neighbor to non-MCMS applications.
Every request passes the ISAPI filter and is checked against the root
channels before it is either passed to MCMS or to IIS.
The more root channels you have the more comparisons need to be done. So to
ensure that non-MCMS content is not slowed down to much you should not have
to many root channels.

But if your server is only a MCMS server with less content on the file
system, then only the 200-300 item rule applies.

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


"Tony Fabian" <Tony@fabian.dk> wrote in message
news:%23WXRwSSrFHA.3444@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> I have a question regarding a statement in the MCMS Faq.
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm#4009EC9B-3902-4625-93EB-B6F5777BDDF2
>
> In the section "Is there a limitation for Postings per Channel?" it says
> "Root Channel containers:
> Limit the number of containers under the root node. (For example,
> /Channels should not have more than 10 to 15 immediate children
> containers.) "
>
> What impact does it have if there is more than 10 - 15 immediate childrens
> of the Channels node?
> Currently we have around 50 containers under the root channel node and
> around the same amount of containers under the root ressourcegallery node.
>
> Would it make any difference in terms of performacne to have a structure
> like this
>
> /Channels/OneChannelContainer/50ChannelContainers instead of
> /Channels/50ChannelContainers
>
> Is the issue only related to poor performance when using the Site Manager
> or does it impact accessing the objects through asp.net?
>
> Kind regards
>
> Tony
>

[ Post a follow-up to this message ]

Thank you Stefan!! :-)

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:Ol17AMUrFHA.1984@tk2msftngp13.phx.gbl...
> Hi Tony,
>
> that is only a rule to let MCMS be a good neighbor to non-MCMS
> applications.
> Every request passes the ISAPI filter and is checked against the root
> channels before it is either passed to MCMS or to IIS.
> The more root channels you have the more comparisons need to be done. So
> to ensure that non-MCMS content is not slowed down to much you should not
> have to many root channels.
>
> But if your server is only a MCMS server with less content on the file
> system, then only the 200-300 item rule applies.
>
> 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
> ----------------------
>
>
> "Tony Fabian" <Tony@fabian.dk> wrote in message
> news:%23WXRwSSrFHA.3444@TK2MSFTNGP12.phx.gbl... 
>
>

[ Post a follow-up to this message ]