Several improvements and fixes for local_thr & remote_thr
Description
Environment
All OS.
Activity
mark February 26, 2013 at 8:35 PM
Here are a couple of usage examples and results:
./local_thr tcp://*:5031 10240124 4000 16000000 16000000 PULL ZMSG 4
RCVBUF=15625 KB SNDBUF=15625 KB adjusted
Threads: 4
PULLING ZMQ_MSG...
Message size: 10000 KBytes, time: 14.024788 secs
Pulled 38.147 GB @ 2.720 GB/s
./remote_zmq tcp://127.0.0.1:5031 10241024 1000 16000000 16000000 PUSH ZMSG 1 4
Threads: 1, workers 4
Worker 0 spawned
Worker 1 spawned
Worker 2 spawned
Worker 3 spawned
RCVBUF=15625 KB SNDBUF=15625 KB adjusted
RCVBUF=15625 KB SNDBUF=15625 KB adjusted
RCVBUF=15625 KB SNDBUF=15625 KB adjusted
RCVBUF=15625 KB SNDBUF=15625 KB adjusted
PUSHING ZMQ_MSG...
PUSHING ZMQ_MSG...
PUSHING ZMQ_MSG...
PUSHING ZMQ_MSG...
Worker 0 joined
Worker 1 joined
Worker 2 joined
Worker 3 joined
Message: size: 10001 KBytes, count: 1000/workers(4), time: 14.667326 secs
Pushed 38.151 GB @ 2.601 GB/s
There are several improvements to the perf test remote_thr & local_thr:
Better timing
Command line option for RCV/SNDBUF
Command line options for threads/workers
Improved and fixed throughput calculations
Added options for sockopt