NetNamedPipe: varying response time when communication is idling

Posted by Sven Künzler on Stack Overflow See other posts from Stack Overflow or by Sven Künzler
Published on 2009-04-19T19:27:03Z Indexed on 2010/05/12 17:24 UTC
Read the original article Hit count: 226

I have two WCF apps communicating one-way over named pipes. All is nice, except for one thing: Normally, the request/response cycle takes zero (marginal) time. However, if there was a time span of, say, half a minute without any communication, the request/response increases up to ~300-500ms.

I looked around the net and I got the idea of using a heart beat/ping mechanism to keep the communication channel busy. Using trial and error I found that when doing a request each 10 seconds, the response times stay low. Starting at around 15s intervals, the "hiccup" response times begin to appear.

Now I'm wondering where this phenomenon is originating from. I tried setting alle conceivable timeouts on both sides to > 1 minute, but that did not help.

Can anybody explain what's going on there?

© Stack Overflow or respective owner

Related posts about .NET

Related posts about wcf