We have a service that is hosted as a Windows service. netTcpBindingwith message security type without reliable session.
On the client side, we have a proxy assembly that is cached in the list as a channel creation, and disposal is expensive. My client connects to the server and receives data from the server.
Now, if I stop the server, then the CPU jumps up. The workflow that the processor consumes is designed to execute code.
void System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, NativeOverlapped *)
When I delete all proxies, the CPU consumption of the client-application becomes nothing. I need to know how we can solve this problem in WCF.
source
share