Skip to content
This repository

local_thr / remote_thr not working as expected #105

Closed
MichaelEwe opened this Issue · 2 comments

2 participants

MichaelEwe John Gozde
MichaelEwe

I testes the throuput benchmark programs in the way described on the zeromq website

  • local_thr tcp://*:5000 256 1000
  • give the local_thr some time time start up (count to 10... ;-)
  • remote_thr tcp://*:5000 256 1000

Using 1000 packages of size 256 Byte works fine. Both programs terminate and the "local" programs reports the performance figures

Situation changes, if you change the package count to 2000. Now only the "remote" program terminates; the "local" program hangs forever. Maybe still waiting for packets.

As a trial I changed the "remote" program to close the socket and to terminate the context. Makes no difference at all.

The corresponding native programs from the zeromq distribution do not show this behaviour,

MichaelEwe

Sorry, the "remote" command line actually is:

  • remote_thr tcp://localhost:5000 256 1000
John Gozde jgoz closed this issue from a commit
John Gozde jgoz Merge branch '105-fix-perf-tests'
Fix #105: use PUSH/PULL for throughput tests (mirrors libzmq)
76404a9
John Gozde jgoz closed this in 76404a9
John Gozde
Collaborator

Fixed this in master. The zeromq distributions use PUSH/PULL sockets but clrzmq was using PUB/SUB, which can drop messages when they get sent at lightning speeds.

Thanks for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.