locked
NetNamedPipe: varying response time when communication is idling RRS feed

  • Question

  • 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.

    Searching this forum, 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 secs, the response times stay low. Starting at around 15 secs 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?

    Thanks,
    Sven
    Tuesday, March 3, 2009 8:09 PM