Menu
I have searched the internet for how to increase memory and cache size for application pools in IIS 7 but all topics are diffused and I don't know the effect of combining those settings together.
Can somebody describe how I can increase memory and cache size for application pools in IIS 7?
763
You can increase this amount by opening the IIS manager (start->run->inetmgr), expanding the server node on the left pane, clicking on "Application Pools", right clicking on the application pool running your application, selecting "Advanced Settings", and changing the Private Memory Limit and Virtual Memory Limit in ...
To answer the question of process v. pool identification, we need to open IIS Manager, click on the root of the navigation tree (the server name) and under IIS double click the Worker Processes icon. This will open a view that lists the running working processes, their process IDs, CPU and most memory usage.
Default application pools have private memory of 0 KB, which means there is no limit. Therefore, according to your server resources, you can run as many websites as you wish under the default application pool.
Go to Tools & Settings > IIS Application Pool:Recycling at regular time intervals (minutes) Recycling when the maximum number of requests is reached. Recycling when the maximum amount of virtual memory is used. Recycling when the maximum amount of private memory is used.
In my understanding output cache can be set only at the IIS level and not specifically for an application pool. Whatever is set at the IIS level is applied to all the web sites under it. So effectively you can apply a max cache size at the web application level.
If you are using windows 7 professional (IIS features vary depending on the operating system) if you open IIS manager and click on the server name, in the features view there is an Output Caching feature. You can edit that to set the max cache size. If you set it to a very high value, it will use up a lot of your RAM and could deteriorate the performance of the whole box.
THe application pool itself can have a private memory limit and a virtual memory limit.
Primary memory limit: Maximum amount of private memory (in KB) a worker process can consume before causing the application pool to recycle.
Virtual memory Limit: Maximum amount of virtual memory (in KB) a worker process can consume before causing the application pool to recycle.
Both the above settings are set to 0 by default, which means there is no limit set.
Long story short: Raising the output cache size at the IIS server level is the best option that suits your needs.
192
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
