>>How did you determine that this is the case? What degradation did you find when using just one instance ?
>
>If the worker process is allocated to process a hit, if no more is available, this will create a queue. We have a rate of 12 hits a second during the day. Despite the fact that most hits are answered in 0.1 to 0.3 second, some of them are sometimes taking a few seconds. The 2nd, 3rd and 4th worker process are really useful in that case. Sometimes, when all the four are allocated to answer a hit, all incoming hits qo in a queue until one is available. But, that is very rare and would last only for some fraction of a second.
Sounds like you need the extra processes then. Long term it might well be worth looking to make some of the long running hits async - but that would depend on why they take so long...
>>Pretty sure that you can. If IIS8 Express works (
http://www.microsoft.com/en-gb/download/details.aspx?id=34679) then I'd assume same for full IIS8?
>
>IIS 7 is built in the OS. I thought that IIS 8 was only available to Windows Server 2012, which I believe it is the new IIS version to be part of that OS. I did not know we were able to install a full version of IIS 8 to be downloaded and installed on Windows Server 2008. I do not know however if all the full capabilities would be able to be seen on that OS.
You're right, IIS8 is only for W2012 and W8. I'm behind the curve on this :-{
>>MS might duck the issue if non-MS technologies are involved :-{
>
>We'll have to wait and see. :)
Let us know how things progress.
BTW, off topic a bit, I found this a good overview of IIS architecture (3 parts) :
http://www.youtube.com/watch?v=haYiSvvDNYQ
