For the most part, CMS (2002) works fine, but about once a week we run into 
a bit of an issue which brings our Intranet site to its knees.  On Monday mo
rnings we release a series of weekly news articles.  As the majority of peop
le (approx. 3000) read thes
e new articles first thing when they get in on Monday, our site gets complet
ely hammered.  If the site doesn't actually time out; pages can easily take 
2 or 3 minutes to load (per person).

We've already implemented caching for our header bar and footer bar, but bec
ause there are a number of different permissions on the site; we can't cache
 the entire page as items such as navigation, menus, etc. could be different
 for each individual.

Would caching the placeholder content make any improvements?  Is there some 
other method(s) that we could also use to eliminate the problem?  Any help i
s appreciated.

Thanks.

-JR

[ Post a follow-up to this message ]

Sorry, forgot to add that our max. node size is currently set to 15000 and t
he disk cache is 2GB.

[ Post a follow-up to this message ]

You can output-cache the other elements of your page (or maybe even the
whole page) by role, so everyone with the same permissions as each other
sees their version of the cached content.

Take a look at this document:
http://msdn.microsoft.com/library/e...
92f3a7969.asp

--
Glen Wells
www.cubik.co.uk


"JR" <confused@times> wrote in message
news:%23A6GxtbdFHA.3396@TK2MSFTNGP10.phx.gbl...
> For the most part, CMS (2002) works fine, but about once a week we run
> into a bit of an issue which brings our Intranet site to its knees.  On
> Monday mornings we release a series of weekly news articles.  As the
> majority of people (approx. 3000) read these new articles first thing when
> they get in on Monday, our site gets completely hammered.  If the site
> doesn't actually time out; pages can easily take 2 or 3 minutes to load
> (per person).
>
> We've already implemented caching for our header bar and footer bar, but
> because there are a number of different permissions on the site; we can't
> cache the entire page as items such as navigation, menus, etc. could be
> different for each individual.
>
> Would caching the placeholder content make any improvements?  Is there
> some other method(s) that we could also use to eliminate the problem?  Any
> help is appreciated.
>
> Thanks.
>
> -JR

[ Post a follow-up to this message ]