HornetQ Paging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
HornetQ can manage addresses containing a large number of messages even if the memory available to the browser is limited. It does so by ''paging'' messages from memory on persistent storage and back in memory as they are needed, thus maintaining a low memory footprint. | HornetQ can manage addresses containing a large number of messages even if the memory available to the browser is limited. It does so by ''paging'' messages from memory on persistent storage and back in memory as they are needed, thus maintaining a low memory footprint. | ||
Paging starts as soon a a memory threshold set per [[WildFly HornetQ-Based Messaging Subsystem Concepts#Address|address]] is reached. | |||
By default, there is no paging - paging has to be explicitly enabled in configuration. | |||
=Configuration= | |||
<font color=red>'''TODO''' http://docs.jboss.org/hornetq/2.4.0.Final/docs/user-manual/html/paging.html</font> | |||
Latest revision as of 00:45, 12 March 2016
Internal
Overview
HornetQ can manage addresses containing a large number of messages even if the memory available to the browser is limited. It does so by paging messages from memory on persistent storage and back in memory as they are needed, thus maintaining a low memory footprint.
Paging starts as soon a a memory threshold set per address is reached.
By default, there is no paging - paging has to be explicitly enabled in configuration.
Configuration
TODO http://docs.jboss.org/hornetq/2.4.0.Final/docs/user-manual/html/paging.html