<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [rabbitmq-discuss] High cpu usage for Java RabbitMQ client? (solved, my fault)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Matthias,<BR>
<BR>
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. :)<BR>
<BR>
>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?<BR>
<BR>
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?<BR>
<BR>
Thank you,<BR>
Rob<BR>
<BR>
> Looks fairly sane. The connection thread sits exactly where you'd expect<BR>
> it to be when not much is happening on the connection, namely in a<BR>
> socketRead0. There are a whole bunch of non-rabbit threads though,<BR>
> including UI threads. It would be good to eliminate those from our<BR>
> enquiries.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>