"alex" <alex.TakeThisOut@discussions.microsoft.com> wrote in message
news:DB7F6546-1849-47B6-B1B5-83B27D35D403@microsoft.com...
>i have about 20 or so sites which is hosted a server that has w2k3 web
> edition and 640 megs of ram. I also have .net 1.1 and now 2.0 for certain
> sites and i have split the versions of .net sites into sperate application
> pools so there's no problems. On this server, i started noticing that alot
> of
> ram is being ate up and leaving the server with about 129 or less of
> memory
> what can i do prevent this?
You can open the IIS manager, and to the application pools, you start
allocating websites to application pools. However, by default, this is
already allocated as a ' default pool '. and .NET 2.0 has another
application pool
> P.s adding more ram not really an option because this server will be
> replaced before the end of 06.
You can limit some memory, using these settings. But I really think, that
you should think about more memory. Never believe the '640K memory should be
sufficient' myth
You also can save some memory by disabling unnecessary processes and by
logging off the console (that uses at +/- 128 MB)