My workers processes cap out at 70mB. How do I raise this limit? I have 4Gb on Windows 2003 IIS6. Thanks!
|
If by "cap out", you mean "consume and stay stable", the short answer is that you don't. The memory limits for recycling are the point at which the process gets shot and killed, but the process needs to grow to that size first. Bad Simile Warning It's like having a policy that any plant growing taller than 1 metre will be ripped out and re-seeded. If the plant grows to 1 metre, it gets ripped out; if it only ever grows to 20cm, it'll be left alone. There's no way you can artificially inflate a worker process' memory use (other than "write bad or unoptimized code") - busy static file serving sites sometimes run at less than 100MB per worker process, because they've less than 100MB content to serve in the first place. If your sites are performing well, rejoice! They won't be pulled from their flower bed. |
|||
|
|
|
In Internet Information Services (IIS) Manager, go to
This blog post on MSDN explains when to configure memory recycling:
|
||||
|
|
|
Open inetmgr on the server (run + inetmgr), go to the properties of the application pools, and in the memory recycling section you can specify how much virtual memory the pools will use. |
|||
|
|
