[zeromq-dev] Windows throughput perfomance. Once again.
sustrik at 250bpm.com
Tue May 31 12:50:31 CEST 2011
On 05/31/2011 12:42 PM, Геннадий Казачёк wrote:
> I tried to profile zmqlib, but spent only a couple of hours, so the only
> thing I've found was:
> ELAPSED TIME (seconds)
> zmq :: select_t :: loop - 225,44
This is an infinite loop.
> zmq :: mailbox_t :: recv - 112,85
This is a blocking function. When nothing happens application threads
> I guess (correct me, if I wrong) that this means, that we are waiting
> for something 1000 times longer then working.
Well. It looks like the application threads is waiting for 112.85 sec
out of total 225.44 sec.
> I can make another test, but don't know what exactly.
Try to find out what is the application thread actually waiting for and
why it takes so long. Is it one 2 minute sleep or is it many small
sleeps that add to 2 minutes? Etc.
More information about the zeromq-dev