Re: [zeromq-dev] DEALER -- ROUTER -- Double Read() is so slow. Please have a look at the codes.

2013-04-15 Thread Pieter Hintjens
On Mon, Apr 15, 2013 at 8:02 AM, crocket crockabisc...@gmail.com wrote: If I call Read Tag from DSCTagTest via ZeroMQ, it takes 350~370ms to call Read Tag 1000 times. This is doing a round-trip, right? That becomes slow. There's a lot of latency for pushing single messages through the whole

Re: [zeromq-dev] DEALER -- ROUTER -- Double Read() is so slow. Please have a look at the codes.

2013-04-15 Thread crocket
In other words, I send 1000 requests and then retrieve 1000 results later. Each message from DEALER to ROUTER causes LabVIEW to call Read Tag and send back the result to DEALER. Is it still a round-trip? ___ zeromq-dev mailing list

Re: [zeromq-dev] DEALER -- ROUTER -- Double Read() is so slow. Please have a look at the codes.

2013-04-15 Thread Pieter Hintjens
On Mon, Apr 15, 2013 at 9:56 AM, crocket crockabisc...@gmail.com wrote: In other words, I send 1000 requests and then retrieve 1000 results later. Each message from DEALER to ROUTER causes LabVIEW to call Read Tag and send back the result to DEALER. Is it still a round-trip? No, this would

Re: [zeromq-dev] DEALER -- ROUTER -- Double Read() is so slow. Please have a look at the codes.

2013-04-15 Thread crocket
I'd try more messages, see if the time is proportional (10K, 100K, 1M). I'd then replace the LabView piece with null code (doing no work) so you can see which side the time is being taken. It turned out that labview-zmq(LabVIEW binding) itself was slow. labview-zmq is just a wrapper around

Re: [zeromq-dev] DEALER -- ROUTER -- Double Read() is so slow. Please have a look at the codes.

2013-04-15 Thread Joshua Foster
JeroMQ is going to be slower than the JZMQ. Joshua crocket April 15, 2013 8:22 PM I'd try more messages, see if the time is proportional (10K, 100K, 1M). I'd then replace the LabView piece with null code (doing no work) so you can see which side the time is being