From: fort frances.on.ca
In the cache settings on the advanced tab, there is a setting for "Percentage of available memory to use for caching" but regardless of what I increase the number to, it will not use the memory. I started off building the server with 1 gig of RAM and then decided to toss in another 2 gig for a total of 3 gig. Is there some undocumented upper limit on the size of RAM cache?
Based on my understanding of percentages, by tripling the amount of RAM, the RAM cache should have nearly tripled too but that is not the case.
In the event log, I have:
quote:Event Type: Warning Event Source: Microsoft ISA Server Web Proxy Event Category: None Event ID: 14193 Date: 4/12/2005 Time: 10:41:34 PM User: N/A Computer: FFISA Description: Cache was initialized with less cache memory than was configured. This is because there is not enough free memory available for ISA Server caching.
From: fort frances.on.ca
Dang. Nobody have anything to say? Somebody must be running ISA with more than a gig of RAM. It is a waste of money then to toss anothet 2 gig in the box to only have the MSDE eventually swallow it up.
Looking in task manager now, I have: sqlservr.exe 1,716,692 K wspsrv.exe 471,472 K
RE: Percentage of available memory to use for caching - 14.Apr.2005 7:46:00 PM
I've got 2GB of ram in my ISA box with the setting set to %60 and it's using 497MB of RAM. I did notice that when I upped it from %50 to %60 that the page file increased tremendously, but the physical usage only went up by about 20MB.
Of course, the setting says "Percentage of FREE memory to use for caching." If you're running more than ISA on your box than ISA, then it will have less free memory to allocate because other processes are using up the free RAM. I imagine if you moved your logs to an off server SQL Database that might give you more RAM usage.
I had a problem with SQLSVR.exe taking up all the free memory on my ISA server. myxiplx helped me out with the information below. If fixed the problem by limiting the amount of memory that sqlsvr can use. This may not fix your problem with the cache memory, but it helped my box run better.
There is a 'max server memory' option in SQL and MSDE, with the default being 2147483647Mb! However it is possible to change this using the osql utility installed with MSDE. I haven't run this long enough on our server to test, but believe it will work according to Microsoft's documentation.
It appears that by default SQL Server, and MSDE will grab as much memory as they can since they assume that they are on a dedicated database server. MS seem to imply that the 'max server memory' parameter should be set if the server isn't exclusively a SQL server here. Microsoft also have more details on the max and min memory parameters.
I then found this page with details of the scripts to configure these paramaters, and this knowledgebase article explaining how to use osql. With these two articles, it is possible to reset the 'max server memory' parameter, with the change taking effect immediately.
You will need to know the SQL instance name to use osql and this can be found in the Services list. In my case, the service was named MSSQL$MSFW and MSFW is the instance name.
Two scripts are shown below, one to check your server's max memory setting, and one to change the value.
To view the memory on your server, copy the following commands to a text file (eg. c:\checkmemory.sql):
From: fort frances.on.ca
Thanks, I did see that post about limiting MSDE. I also got a link from M$ to http://support.microsoft.com/?id=325003 and gave them both to my DBA to look at. She is much smarter than me (when it comes to SQL anyway ) and she limited SQL now to 1024 MB.
Still, I get the "Cache was initialized with less cache memory than was configured" which I don't understand. When I boot the box, PF Usage starts off at around 1.6 GB with sqlservr.exe using around 100,000 K and growing.
I started out increasing the RAM cache for 10% to 60% and then 80% but still the error. AmI understanding the setting wrong? If I change it back to 10%, the PF Usage goes way down, the memory footprint for wspsrv.exe drops to around 121,992 K, and the event log no longer shows the error.
Change it to 20% and the PF Usage goes up, the memory footprint for wspsrv.exe increases to around 212,000 K, and the event log shows no error.
Change it to 30% and the PF Usage goes up some more, the memory footprint for wspsrv.exe increases to around 301,000 K, and the event log shows no error.
More of the same for 40% and 50%, but as soon as I try 60% I get the error and nothing above that increases the PF Usage. I have to assume that there is an upper limit that the manual does not mention and the 100% mentioned in the manual is some theoretical value.
Is there anyone out there that has different results?
It only makes mention of ISA 2000 the math does not work out. I have 3 gig and 60% of that is not the 2 gig limit discussed. Combined however with the base memory requirement for the OS and the 1 gig for MSDE, 60% of "Total" memory would put me over the top.