You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2015/03/03 12:21:11 UTC
svn commit: r942122 - in /websites/production/activemq/content:
cache/main.pageCache
how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html
scaling-the-depth-of-a-queue.html
Author: buildbot
Date: Tue Mar 3 11:21:10 2015
New Revision: 942122
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html
websites/production/activemq/content/scaling-the-depth-of-a-queue.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html
==============================================================================
--- websites/production/activemq/content/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html (original)
+++ websites/production/activemq/content/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html Tue Mar 3 11:21:10 2015
@@ -82,15 +82,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent">Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.
-
-<p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p>
-
-<p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persistent messages.</p>
-
-<p>For more information - see below: </p>
-
-<h2 id="HowdoIconfigureActiveMQtohold100sofmillionsofQueueMessages?-MessageCursors">Message Cursors</h2>
+<div class="wiki-content maincontent">Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.<p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p><p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persisten
t messages.</p><p>For more information - see below:</p><p></p><h2 id="HowdoIconfigureActiveMQtohold100sofmillionsofQueueMessages?-MessageCursors">Message Cursors</h2>
<p>A common problem in previous versions of ActiveMQ was <a shape="rect" href="my-producer-blocks.html">running out of RAM buffer</a> when using non-persistent messaging.</p>
Modified: websites/production/activemq/content/scaling-the-depth-of-a-queue.html
==============================================================================
--- websites/production/activemq/content/scaling-the-depth-of-a-queue.html (original)
+++ websites/production/activemq/content/scaling-the-depth-of-a-queue.html Tue Mar 3 11:21:10 2015
@@ -82,15 +82,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.</p>
-
-<p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p>
-
-<p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persistent messages.</p>
-
-<p>For more information - see below: </p>
-
-<h2 id="ScalingtheDepthofaQueue-MessageCursors">Message Cursors</h2>
+<div class="wiki-content maincontent"><p>Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.</p><p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p><p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the pe
rsistent messages.</p><p>For more information - see below:</p><p></p><h2 id="ScalingtheDepthofaQueue-MessageCursors">Message Cursors</h2>
<p>A common problem in previous versions of ActiveMQ was <a shape="rect" href="my-producer-blocks.html">running out of RAM buffer</a> when using non-persistent messaging.</p>