Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

This closes #530

This commit is contained in:
Clebert Suconic 2016-05-23 13:31:00 -04:00
parent c4b29b69b3 c0ec7e2ff8
commit 8df8d76163
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user-manual/en/jms-bridge.md
View File

@ -26,7 +26,7 @@ JMS servers, as long as they are JMS 1.1 compliant.
> >
> Do not confuse a JMS bridge with a core bridge. A JMS bridge can be > Do not confuse a JMS bridge with a core bridge. A JMS bridge can be
> used to bridge any two JMS 1.1 compliant JMS providers and uses the > used to bridge any two JMS 1.1 compliant JMS providers and uses the
> JMS API. A core bridge (described in [Core Bidges](core-bridges.md)) is used to bridge any two > JMS API. A core bridge (described in [Core Bridges](core-bridges.md)) is used to bridge any two
> Apache ActiveMQ Artemis instances and uses the core API. Always use a core bridge if > Apache ActiveMQ Artemis instances and uses the core API. Always use a core bridge if
> you can in preference to a JMS bridge. The core bridge will typically > you can in preference to a JMS bridge. The core bridge will typically
> provide better performance than a JMS bridge. Also the core bridge can > provide better performance than a JMS bridge. Also the core bridge can

2
docs/user-manual/en/paging.md
View File

@ -115,7 +115,7 @@ This is the list of available parameters on the address settings.
</tr> </tr>
<tr> <tr>
<td>`page-max-cache-size`</td> <td>`page-max-cache-size`</td>
<td>The system will keep up to \<`page-max-cache-size` page files in memory to optimize IO during paging navigation.</td> <td>The system will keep up to `page-max-cache-size` page files in memory to optimize IO during paging navigation.</td>
<td>5</td> <td>5</td>
</tr> </tr>
</tbody> </tbody>

2
docs/user-manual/en/send-guarantees.md
View File

@ -101,7 +101,7 @@ server and the client of 0.25 ms.
With a RTT of 0.25 ms, the client can send *at most* 1000/ 0.25 = 4000 With a RTT of 0.25 ms, the client can send *at most* 1000/ 0.25 = 4000
messages per second if it blocks on each message send. messages per second if it blocks on each message send.
If each message is \< 1500 bytes and a standard 1500 bytes MTU size is If each message is < 1500 bytes and a standard 1500 bytes MTU (Maximum Transmission Unit) size is
used on the network, then a 1GiB network has a *theoretical* upper limit used on the network, then a 1GiB network has a *theoretical* upper limit
of (1024 \* 1024 \* 1024 / 8) / 1500 = 89478 messages per second if of (1024 \* 1024 \* 1024 / 8) / 1500 = 89478 messages per second if
messages are sent without blocking! These figures aren't an exact messages are sent without blocking! These figures aren't an exact