[rabbitmq-discuss] Java client - 91% time spent in reading the socket?
mklishin at gopivotal.com
Thu Aug 1 19:03:16 BST 2013
> The other 9% is spent in "my code". Is it really true that it is so time consuming for the connection thread to need 9/10ths of the time?
What profiler do you use? Sampling profilers don't measure for how long every method is executed,
just at what points in time a particular method was running. For the main loop I can imagine it greatly
skews the results
> Also - I'm only seeing 400msg/s (even when I comment out all my code) from a durable persistent queue with ACK, lending more weight to my suspicions that something is not quite right here (I have basic QoS at 100msg and a single thread+channel here).
It's a low rate. You can try automatic acknowledgements just to compare. Throughput in both directions
also depends on message payload size and TCP stack settings. RabbitMQ Java client by default
disables Nagle's algorithm.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the rabbitmq-discuss