|
Home > Archive > Microsoft Content Management Server > March 2005 > Node cache advise
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]
|
|
| Dominik 2005-03-23, 7:47 am |
| Hello,
we are currently trying to define node chache settings on our CMS site. Our
productive servers have 2 gig of RAM. The problem we encounter is that the
SQL query script from http://support.microsoft.com/default.aspx?id=318976
returns a number of over 300.000.
It is stated that you should use the returned number but not go over 35.000
in the settings. How can we proceed with such a high number of 300.000? Is
35.000 setting in node cache anywhere realistic / feasible in such a scenario?
Thanks a lot,
Dominik
| |
| Stefan [MSFT] 2005-03-23, 7:47 am |
| Hi Dominik,
setting a higher value as 35000 can cause problems as the usable memory is
only around 800 MB.
The nodes differ in size depending on the placeholder content.
So you could increase the value and test if the memory and performance
becomes better or not.
Actually I think it will not be possible to increase it up to 300000
I would suggest to do some loadtesting against the site. Then monitor the
size of the application pool process. If it is below 750 MB you can increase
the value.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights
Book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Dominik" <Dominik@discussions.microsoft.com> wrote in message
news:90836CF4-2B6D-4505-9748-D619A1DC56C2@microsoft.com...
> Hello,
>
> we are currently trying to define node chache settings on our CMS site.
Our
> productive servers have 2 gig of RAM. The problem we encounter is that the
> SQL query script from http://support.microsoft.com/default.aspx?id=318976
> returns a number of over 300.000.
> It is stated that you should use the returned number but not go over
35.000
> in the settings. How can we proceed with such a high number of 300.000? Is
> 35.000 setting in node cache anywhere realistic / feasible in such a
scenario?
>
> Thanks a lot,
> Dominik
|
|
|
|
|