[Spread-users] 1225

Jonathan Stanton jonathan at cnds.jhu.edu
Thu Mar 7 02:23:39 EST 2002

On Wed, Mar 06, 2002 at 06:39:43PM +0100, koorosh.alahiari at ids.allianz.com wrote:
> Hi All,
> I have done some performance testing & find that
> Sending is a little over twice as fast as
> Receiving and this is why Rceivers
> get shot down by spread since eventually
> spread is going to reach its backlog
> limit.
> My Senders & Receivers (one of each)
> do very little else but sending and receiving
> in a tight loop.
> Does this make sense?

Yes. In any application you will need to do some flow-control or
synchronization between the senders and receivers unless you want to drop

Since spread is designed from a reliable transpot point-of-view it
doesn't drop messages. Spread does support "unreliable" messages which can
be dropped, but it currently doesn't drop them when the receive queue fills
up (that would not be hard to chagne though)

So you need to include flow control in whatever application you are
designing and then the problem should go away.

Jonathan R. Stanton         jonathan at cs.jhu.edu
Dept. of Computer Science   
Johns Hopkins University    

More information about the Spread-users mailing list