a few tiny doc typos
This commit is contained in:
parent
c4b29b69b3
commit
c0ec7e2ff8
|
@ -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
|
||||
> 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
|
||||
> 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
|
||||
|
|
|
@ -115,7 +115,7 @@ This is the list of available parameters on the address settings.
|
|||
</tr>
|
||||
<tr>
|
||||
<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>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
@ -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
|
||||
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
|
||||
of (1024 \* 1024 \* 1024 / 8) / 1500 = 89478 messages per second if
|
||||
messages are sent without blocking! These figures aren't an exact
|
||||
|
|
Loading…
Reference in New Issue