Last post Dec 21, 2005 02:20 PM by TimGT
Dec 20, 2005 11:54 AM|TimGT|LINK
Is there any disadvantage to having more than 1 IIS worker process for DNN? As in, if you are editing a page, then hit submit, does it use a different worker process, and would that mess things up?
Dec 20, 2005 02:07 PM|smiling4ever|LINK
The recomended worker processors for any application pool are 2. The advantage of using two is that when one procesor fail the other will work with no downtime. However the disadvantage is that each worker processor will consume large amount of the commit
Dec 20, 2005 04:17 PM|jking078|LINK
In order to have more than 1 worker process, you are basically referring to what IIS calls a "web garden". Yes there are advantages such as ability to handle multiple requests simultaneously with more efficiency. And yes there are disadvantages such as
consuming more RAM. But RAM is cheap.
As for DNN, you will have to follow the "web farm" documentation and set DNN as it were running on multiple servers. That is because each worker is separate, exactly as is the worker processes were on separate machines. So, you will need disk based caching
and the web.config settings, etc.
Dec 21, 2005 01:06 AM|TimGT|LINK
Could you point me out where this documentation is please?
Dec 21, 2005 01:43 PM|jking078|LINK
Dec 21, 2005 02:20 PM|TimGT|LINK
I roll around 150,000 pageviews a day on my DNN setup.. I think another worker process might be handy.