<div class="docbook"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">9.9. Message Compression</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Java-Broker-Runtime-Background-Recovery.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Runtime</th><td width="20%" align="right"> <a accesskey="n" href="Java-Broker-Runtime-Connection-Limit.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Java-Broker-Runtime-Message-Compression"></a>9.9. Message Compression</h2></div></div></div><p>The Apache Qpid Broker-J supports<a href="#ftn.d0e9358" class="footnote" id="d0e9358"><sup class="footnote">[10]</sup></a> message compression. This feature works in co-operation with Qpid
  Clients implementing the same feature.</p><p>Once the feature is enabled (using Broker context variable
   <span class="emphasis"><em>broker.messageCompressionEnabled</em></span>), the Broker will advertise support for the
  message compression feature to the client at connection time. This allows clients to opt to turn
  on message compression, allowing message payload sizes to be reduced.</p><p>If the Broker has connections from clients who have message compression enabled and others who
  do not, it will internally, on-the-fly, decompress compressed messages when sending to clients
  without support and conversely, compress uncomressed messages when sending to clients who do.</p><p>The Broker has a threshold below which it will not consider compressing a message, this is
  controlled by Broker content variable
   (<code class="literal">connection.messageCompressionThresholdSize</code>) and expresses a size in bytes.</p><p>This feature <span class="emphasis"><em>may</em></span> have a beneficial effect on performance by:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Reducing the number of bytes transmitted over the wire, both between Client and Broker, and
    in the HA case, Broker to Broker, for replication purposes.</p></li><li class="listitem"><p>Reducing storage space when data is at rest within the Broker, both on disk and in
    memory.</p></li></ul></div><p>Of course, compression and decompression is computationally expensive. Turning on the feature
  may have a negative impact on CPU utilization on Broker and/or Client. Also for small messages
  payloads, message compression may increase the message size. It is recommended to test the feature
  with representative data.</p><div class="footnotes"><br /><hr style="width:100; text-align:left;margin-left: 0" /><div id="ftn.d0e9358" class="footnote"><p><a href="#d0e9358" class="para"><sup class="para">[10] </sup></a>Message compression is not yet supported for the 1.0
    protocol.</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-Runtime-Background-Recovery.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-Runtime.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Runtime-Connection-Limit.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">9.8. Background Recovery </td><td width="20%" align="center"><a accesskey="h" href="Apache-Qpid-Broker-J-Book.html">Home</a></td><td width="40%" align="right" valign="top"> 9.10. Connection Limits</td></tr></table></div></div>