[rabbitmq-discuss] High cpu usage for Java RabbitMQ client? (solved, my fault)
Elsner, Robert
Robert.Elsner at echostar.com
Wed Mar 25 02:20:40 GMT 2009
Matthias,
Good news, as you expected, it was something I was doing. There was a Thread.yield() in a loop, which would have caused the extra system time. All is well with RabbitMQ, as you assumed. Sometimes it takes a second opinion, I just hate to waste your time being that. :)
>From my previous email, does the Qos work like I describe? If messages are marked immediate but the client's queue is over Basic.Qos setting, the server will silently drop the delivery?
Also, I have looked through the AMQP lists a little bit and saw some discussion of a compressed or binary wire format, specifically relating to market quotes. It looks like this is slated for 1.0, but that would be ideal for me (since AMQP overhead is ~30-50% of my message size now). Is there a roadmap to adoption?
Thank you,
Rob
> Looks fairly sane. The connection thread sits exactly where you'd expect
> it to be when not much is happening on the connection, namely in a
> socketRead0. There are a whole bunch of non-rabbit threads though,
> including UI threads. It would be good to eliminate those from our
> enquiries.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090324/0754fdc8/attachment.htm
More information about the rabbitmq-discuss
mailing list