: What is the advantage of increasing "maximum worker processes" in IIS? What is the advantage of upping the "Maximum Worker Processes" from the default of 1 in IIS? Given that it seems any worker
What is the advantage of upping the "Maximum Worker Processes" from the default of 1 in IIS?
Given that it seems any worker process can reply to a request from a single client (ie they are not assigned a client) and that session variables are only accessible from the process they were created in, in what situation would it be advantageous to increase this setting?
I ask because one of my web applications was having all sorts of issues with session variables (random logging out etc) - it turns out a server tech had upped this to 4, thinking he was doing good. Returned it to 1 and the application is happy.
More posts by @Merenda212
1 Comments
Sorted by latest first Latest Oldest Best
The only real advantage of increasing the number of worker processes is if you've got some long running process that's blocking the other threads from running - in which case you might want to consider adding another Worker Process.
However, as you've found this basically spools up another instance of w3wp.exe with it's own memory space that doesn't share in-process information between them, so you need to ensure you're set up for session sharing (MachineKey has been set, session is stored in a database or Session Service, etc.). A better option would be looking to see if you can offload the long running process to a separate process altogether.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.