IIS not using all available free memory

Hi,

Modify c:\boot.ini
to start windows with the /3GB switch.

If you are -really- concerned about having as much cache as possible, go
64-bit!
You will see enormous scalability boosts!
I have running such a system, and really most memory operatoins are already
twice as fast. Especially if you need gygabites of cache, 64-bit is -the-
way to go.

Note: If you upgrade to Windows X64, 95% of the 32-bit programs you run on
that systems continue to work. What needs attention if you have ***custom***
32bit COM components written in VB6 or in C++. VB6 COM components cannot run
in a 64bit env, but C++ components can be recompiled.

<omark DeleteThis @jeeran.com> wrote in message
news:1160467738.742458.56140@m7g2000cwm.googlegroups.com...
>I have 4gb of memory installed on a heavily loaded server w2k3/IIS6
> with gigs of static content, and with all the tweaking to IIS, I can
> not make it use more than 2GB of cache, is there a setting somewhere in
> windows server or IIS that needs to be modified in order to go above
> this threshold ?
>
 >> Stay informed about: IIS not using all available free memory 

<omark.TakeThisOut@jeeran.com> wrote in message
news:1160478429.317170.146370@c28g2000cwb.googlegroups.com...
> Thanks a lot Egbert, that did it!! I will take your recommendation on
> 64bit processing.
>
> While we are on the subject of IIS and caching, what is the difference
> between the setting ObjectCacheTTL setting, and the http.sys caching

good question. I think but not for 100% sure that ObjectCacheTTL is a
cache at the IIS resource based level such as scripts, blobs (images),
directory listing caches etc.
While a Uri identifies resources by Universal Resource Identifier for
instance http://www.yourserver.com/yourpage.aspx
Behind the .aspx are several theorecticall files on NTFS, but the output
could be cached as a whole since this is a Uri.


Objects in the Memory Cache will be phased out of the cache if there have
been no references to an object after this period. If system memory is
limited, a lower TTL may be useful to prevent non-paged memory being used
for cached file handles. A value of 0xFFFFFFFF disables the object cache
scavenger. Units are in seconds.
ObjectCacheTTL REG_DWORD
Range: 0 - 0x7FFFFFFF, 0xFFFFFFFF Default:10*60(10Minutes)
Description: INTERNAL ANALYSIS
UriScavengerPeriod 120 (seconds) 10 - 0xFFFFFFFF seconds Determines the
frequency of the cache scavenger. Any response or fragment that has not been
accessed in the number of seconds equal to UriScavengerPeriod is flushed. >
setting UriScavengerPeriod?> > > > On Oct 10, 10:41 am, "Egbert Nierop \(MVP
for IIS\)"> <egbert_nie....TakeThisOut@nospam.invalid> wrote:>> Hi,>>>> Modify
c:\boot.ini>> to start windows with the /3GB switch.>>>> If you are -really-
concerned about having as much cache as possible, go>> 64-bit!>> You will
see enormous scalability boosts!>> I have running such a system, and really
most memory operatoins are already>> twice as fast. Especially if you need
gygabites of cache, 64-bit is -the->> way to go.>>>> Note: If you upgrade to
Windows X64, 95% of the 32-bit programs you run on>> that systems continue
to work. What needs attention if you have ***custom***>> 32bit COM
components written in VB6 or in C++. VB6 COM components cannot run>> in a
64bit env, but C++ components can be recompiled.>>>> <o....TakeThisOut@jeeran.com> wrote
in messagenews:1160467738.742458.56140@m7g2000cwm.googlegroups.com...>>>> >I
have 4gb of memory installed on a heavily loaded server w2k3/IIS6>> > with
gigs of static content, and with all the tweaking to IIS, I can>> > not make
it use more than 2GB of cache, is there a setting somewhere in>> > windows
server or IIS that needs to be modified in order to go above>> > this
threshold ?>
 >> Stay informed about: IIS not using all available free memory