Author: buildbot
Date: Fri Jun 30 20:23:27 2017
New Revision: 1014807
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/apache-activemq-board-report-201707-july.html
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/performance-tuning.html
Modified:
websites/production/activemq/content/apache-activemq-board-report-201707-july.html
==============================================================================
---
websites/production/activemq/content/apache-activemq-board-report-201707-july.html
(original)
+++
websites/production/activemq/content/apache-activemq-board-report-201707-july.html
Fri Jun 30 20:23:27 2017
@@ -72,7 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content
maincontent"><p><strong>Description</strong></p><p><span style="color:
rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source
message-oriented middleware. Apache ActiveMQ is fast, supports many cross
language clients and protocols, comes with easy to use enterprise integration
patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0,
MQTT, Stomp and REST.</span></p><p><strong><span style="color:
rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color:
rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color:
rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color:
rgb(0,0,0);">TODO</span><span style="color: rgb(0,0,0);"><br
clear="none"></span></li></ul></li><li><p><span style="color:
rgb(0,0,0);">ActiveMQ Artemis</span></p></li><ul><li><p><span style="color:
rgb(0,0,0);">TODO</span></p></li></ul><li><span style="color:
rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rg
b(0,0,0);">TODO</span></li></ul></li></ul><p><strong>PMC
changes</strong></p><p><strong>Committer base
changes</strong></p><p><strong>Releases</strong></p><pre> </pre><p>Report not
yet submitted</p><p>(Most of this information is pulled from <a shape="rect"
class="external-link"
href="https://reporter.apache.org/";>reporter.apache.org</a>)</p></div>
+<div class="wiki-content
maincontent"><p><strong>Description</strong></p><p><span style="color:
rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source
message-oriented middleware. Apache ActiveMQ is fast, supports many cross
language clients and protocols, comes with easy to use enterprise integration
patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0,
MQTT, Stomp and REST.</span></p><p><strong><span style="color:
rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color:
rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color:
rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color:
rgb(0,0,0);">Work continues on bug fixes and hardening of the ActiveMQ 5.x
broker.<br clear="none"></span></li><li><span style="color: rgb(0,0,0);">New
5.15.0 release is out which now requires Java 8 and includes the latest Camel
2.19.0 release</span></li></ul><span style="color: rgb(0,0,0);"><br
clear="none"></span></li><l
i><span style="color: rgb(0,0,0);">ActiveMQ
Artemis</span></li></ul><p> </p><ul><li style="list-style-type:
none;background-image: none;"><ul><li><span style="color:
rgb(0,0,0);">Continued work on adding new features</span></li><li><span
style="color: rgb(0,0,0);">Improving AMQP support</span></li><li><span
style="color: rgb(0,0,0);">Many fixes around compatibility with older
clients.</span></li></ul></li></ul><p> </p><ul><li><span style="color:
rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);">The
community has opened up a call for new Logo's for the project website, a vote
to pick a winner is expected late July.<br
clear="none"></span></li></ul></li></ul><p><strong>PMC
changes</strong></p><p><strong>Committer base
changes</strong></p><p><strong>Releases</strong></p><pre> </pre><p>Report not
yet submitted</p><p>(Most of this information is pulled from <a shape="rect"
class="external-link"
href="https://reporter.apache.org/";>reporter.apache.org</a>
)</p></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/performance-tuning.html
==============================================================================
--- websites/production/activemq/content/performance-tuning.html (original)
+++ websites/production/activemq/content/performance-tuning.html Fri Jun 30
20:23:27 2017
@@ -61,7 +61,7 @@
<p></p>
<div class="top_red_bar">
<div id="site-breadcrumbs">
-<a href="using-activemq-4.html">Using ActiveMQ 4</a> > <a
href="performance-tuning.html">Performance Tuning</a>
+<a href="using-activemq.html">Using ActiveMQ</a> > <a
href="performance-tuning.html">Performance Tuning</a>
</div>
<div id="site-quicklinks">
<p><a shape="rect" href="download.html">Download</a> | <a shape="rect"
class="external-link"
href="http://activemq.apache.org/maven/apidocs/index.html";>JavaDocs</a> <a
shape="rect" href="javadocs.html">More...</a> | <a shape="rect"
href="source.html">Source</a> | <a shape="rect"
href="discussion-forums.html">Forums</a> | <a shape="rect"
href="support.html">Support</a></p>
@@ -72,45 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>For a more complete overview see <a
shape="rect" href="performance.html">Performance</a>.</p>
-
-<p>There are trade-offs between performance and reliabilty. <br clear="none">
-By default, activemq strikes a balance between the two, so there are some
things you can change to increase throughput.</p>
-
-
-<h2 id="PerformanceTuning-Asyncpublishing">Async publishing</h2>
-
-<p>First some background:</p>
-
-<p>When an ActiveMQ message producer sends a non-persistent message, its
dispatched asynchronously (fire and forget) - but for persistent messages, the
publisher will block until it gets a notification that the message has been
processed (saved to the store - queued to be dispatched to any active consumers
etc) by the broker. messages are dispatched with delivery mode set to be
persistent by default (which is required by the JMS spec). So if you are
sending messages on a Topic, the publisher will block by default (even if there
are no durable subscribers on the topic) until the broker has returned a
notification. </p>
-
-<p>So if you looking for good performance with topic messages, either set the
delivery mode on the publisher to be non-persistent, or set the
<strong>useAsyncSend</strong> property on the ActiveMQ ConnectionFactory to be
<strong>true</strong>.</p>
-
-<h2 id="PerformanceTuning-Pre-fetchsizesforConsumers">Pre-fetch sizes for
Consumers</h2>
-
-<p>ActiveMQ will push as many messages to the consumer as fast as possible,
where they will be queued for processing by an ActiveMQ Session. The maximum
number of messages that ActiveMQ will push to a Consumer without the Consumer
processing a message is set by the pre-fetch size. You can improve throughput
by running ActiveMQ with larger pre-fetch sizes. Pre-fetch sizes are determined
by the ActiveMQPrefetchPolicy bean, which is set on the ActiveMQ
ConnectionFactory.</p>
-
-<p>Default values:</p>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th
colspan="1" rowspan="1" class="confluenceTh"><p>consumer type</p></th><th
colspan="1" rowspan="1" class="confluenceTh"><p>default
value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
1000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>
queue browser </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
500</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>topic
</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
32767</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>durable topic </p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p> 1000</p></td></tr></tbody></table></div>
-
-
-
-
-
-<h2 id="PerformanceTuning-OptimizedAcknowledge">Optimized Acknowledge</h2>
-
-<p>When consuming messages in auto acknowledge mode (set when creating the
consumers' session), ActiveMQ can acknowledge receipt of messages back to the
broker in batches (to improve performance). The batch size is 65% of the
prefetch limit for the Consumer. Also if message consumption is slow the batch
will be sent every 300ms. You switch batch acknowledgment on by setting the
<strong>optimizeAcknowledge</strong> property on the ActiveMQ ConnectionFactory
to be <strong>true</strong></p>
-
-<h2 id="PerformanceTuning-StraightthroughSessionConsumption">Straight through
Session Consumption</h2>
-
-<p>By default, a Consumer's session will dispatch messages to the consumer in
a separate thread. If you are using Consumers with auto acknowledge, you can
increase throughput by passing messages straight through the Session to the
Consumer by setting the <strong>alwaysSessionAsync</strong> property on the
ActiveMQ ConnectionFactory to be <strong>false</strong></p>
-
-<h2 id="PerformanceTuning-FilebasedPersistence">File based Persistence</h2>
-
-<p>We have a <a shape="rect" href="kaha-persistence.html">file based
persistence store</a> that can be used to increase throughput for the
persistent messages</p>
-
-<h2 id="PerformanceTuning-Performanceguides">Performance guides</h2>
+<div class="wiki-content maincontent"><p>For a more complete overview see <a
shape="rect" href="performance.html">Performance</a>.</p><p>There are
trade-offs between performance and reliability. By default, ActiveMQ strikes a
balance between the two, so there are some things you can change to increase
throughput.</p><h2 id="PerformanceTuning-AsyncPublishing">Async
Publishing</h2><p>First some background:</p><p>When an ActiveMQ message
producer sends a non-persistent message, its dispatched asynchronously (fire
and forget) - but for persistent messages, the publisher will block until it
gets a notification that the message has been processed (saved to the store -
queued to be dispatched to any active consumers etc) by the broker. messages
are dispatched with delivery mode set to be persistent by default (which is
required by the JMS spec). So if you are sending messages on a Topic, the
publisher will block by default (even if there are no durable subscribers on
the topic) until the b
roker has returned a notification.</p><p>So if you looking for good
performance with topic messages, either set the delivery mode on the publisher
to be non-persistent, or set
the <strong><code>useAsyncSend</code></strong> property on the ActiveMQ
ConnectionFactory to be <strong>true</strong>.</p><h2
id="PerformanceTuning-Pre-fetchSizesforConsumers">Pre-fetch Sizes for
Consumers</h2><p>ActiveMQ will push as many messages to the consumer as fast as
possible, where they will be queued for processing by an ActiveMQ Session. The
maximum number of messages that ActiveMQ will push to a Consumer without the
Consumer processing a message is set by the pre-fetch size. You can improve
throughput by running ActiveMQ with larger pre-fetch sizes. Pre-fetch sizes are
determined by the <strong><code>ActiveMQPrefetchPolicy</code></strong>
bean, which is set on the ActiveMQ
<strong><code>ConnectionFactory</code></strong>.</p><p>Default values:</p><div
class="table-wrap"><table class="confl
uenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p>Consumer Type</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>Default Value</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>queue</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><code>1000</code></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>queue browser</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>500</code></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>topic</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><code>32767</code></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>durable topic</p></td><td
colspan="1" rowspan="1"
class="confluenceTd"><p><code>1000</code></p></td></tr></tbody></table></div><h2
id="PerformanceTuning-OptimizedAcknowledge">Optimized Acknowledge</h2><p>When
consuming messages in auto acknowledge mode (set when creating the consumers'
session), A
ctiveMQ can acknowledge receipt of messages back to the broker in batches (to
improve performance). The batch size is 65% of the prefetch limit for the
Consumer. Also if message consumption is slow the batch will be sent every
300ms. You switch batch acknowledgment on by
setting <strong><code>optimizeAcknowledge=true</code></strong> on the
ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2
id="PerformanceTuning-StraightthroughSessionConsumption">Straight through
Session Consumption</h2><p>By default, a Consumer's session will dispatch
messages to the consumer in a separate thread. If you are using Consumers with
auto acknowledge, you can increase throughput by passing messages straight
through the Session to the Consumer by
setting <strong><code>alwaysSessionAsync=false</code></strong> on the
ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2
id="PerformanceTuning-FilebasedPersistence">File based Persistence</h2><p>We
have a <a shape="
rect" href="kaha-persistence.html">file based persistence store</a> that can
be used to increase throughput for the persistent messages</p><p></p><h2
id="PerformanceTuning-Performanceguides">Performance guides</h2>
<p>If you're not convinced by performance reports then please do try running
performance tests yourself. You might wanna check out our overview of <a
shape="rect" href="performance.html">Performance</a> or try using out the <a
shape="rect" href="activemq-performance-module-users-manual.html">ActiveMQ
Performance Module Users Manual</a></p>
