[rabbitmq-discuss] Java client - 91% time spent in reading the socket?

[Michael Klishin]

Tim Robertson:

> Does this look suspicious to anyone?  Can anyone shed any light on how one might improve this?

Java client uses a separate thread for network activity (called "main loop"), one per connection.

So in that thread, 100% of time is spent reading from the socket. When a delivery arrives,
it is dispatched to a work pool (every channel has its own, AFAIR).

If you profile all methods, it's certainly very likely that com.rabbitmq.client.impl.AMQConnection$MainLoop.run will be at the top of
the overall table.

You can try excluding certain classes/methods/threads from the profiler. That will
give you a more informative insight.
--
MK

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130801/e131ca4d/attachment.pgp>