WCF called channel service settings

Question

Is it worth installing a service with the ConcurrencyMode.Multiple and InstanceContextModeMingle.Single attributes to preserve some performance when using named pipes?

I mean, when I do this, I have to worry about multithreading issues.

Answer 1

I automatically use ConcurrencyMode.Multiple for my WCF services because I usually expect the service to be able to handle multiple requests at the same time. For me, this seems to be the most intuitive behavior for the service (i.e. it would be strange if I called the web service and had to wait 10 outstanding requests from other users before they visited me).

Using ConcurrencyMode.Single forces the service to process one request at a time (in the case of multiple requests). This may slow down requests.

, . , WCF . - , , , . , , , , . 5 - , .

, , ConcurrencyMode.Single, - . , , . , . , ConcurrencyMode.Single - , !

Answer 2

? , , , .

? . , .

, .

, .

, , . , (, ), , WCF InstanceContextMode.

, WCF-, .