[Spread-users] Random disconnecting of clients by daemon

Stradling, Joseph W joseph.w.stradling at lmco.com
Fri Aug 28 17:58:53 EDT 2009

Thanks John and Alexey.  I figured it was some sort of buffering issue.
My test was actually a benchmarking test, not typical use.  I wanted to
see how far I could push Spread and so far I have been pleasantly

One question about the underlying communications method.  Does spread
actually multicast between daemons, or is it doing TCP.  I read in the
documentation that as a performance feature spread multicasts between
daemons on the same segment, is this correct?  Also, does Spread do TCP
or Multicast between daemons on different segments?



-----Original Message-----
From: John Schultz [mailto:jschultz at spreadconcepts.com]
Sent: Friday, August 28, 2009 1:39 PM
To: Stradling, Joseph W
Cc: spread-users at lists.spread.org
Subject: Re: [Spread-users] Random disconnecting of clients by daemon

Yes.  You are sending faster than your readers are reading, so buffers
build up on the server until it gets sick of you using too much of its
memory and kicks your connection.

You need to either ensure your readers always process faster than your
writers send or you need to implement some level of flow control.


John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200

On Aug 28, 2009, at 12:30 PM, Stradling, Joseph W wrote:

Hello all,

I'm running some tests with Spread at a very high throughput rate (71
Mbps) with messages which are 1024 bytes in size.  After running my test
for 20 minutes or so, the daemon will disconnect me ( I Get the return
value CONNECTION_CLOSED, when I call SP_receive() )

Is this a buffer issue?

Spread-users mailing list
Spread-users at lists.spread.org

More information about the Spread-users mailing list