Skip to content

Commit 5d748d7

Browse files
committed
Formatting
1 parent 868e511 commit 5d748d7

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

articles/iot-operations/manage-mqtt-broker/howto-configure-availability-scale.md

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -214,28 +214,31 @@ Use this profile when you need to handle a large number of connections and messa
214214

215215
## Calculate total memory usage
216216

217-
The memory profile setting specifies the memory usage for each frontend and backend replica and interacts with the cardinality settings. You can calculate the total memory usage per replica using the formula:
217+
The memory profile setting specifies the memory usage for each frontend and backend replica and interacts with the cardinality settings. You can calculate the total memory usage using the formula:
218218

219-
`M_total = R_fe * M_fe + (P_be * RF_be) * M_be * W_be.`
219+
<!-- M_total = R_fe * M_fe + (P_be * RF_be) * M_be * W_be. -->
220+
221+
$M_{\text{total}} = R_{\text{fe}} \cdot M_{\text{fe}} + (P_{\text{be}} \cdot RF_{\text{be}}) \cdot M_{\text{be}} \cdot W_{\text{be}}$
220222

221223
Where:
224+
222225
| Variable | Description |
223226
|----------|-------------|
224-
| `M_total` | Total memory usage per replica |
225-
| `R_fe` | The number of frontend replicas |
226-
| `M_fe` | The memory usage of each frontend replica |
227-
| `P_be` | The number of backend partitions |
228-
| `RF_be` | Backend redundancy factor |
229-
| `M_be` | The memory usage of each backend replica |
230-
| `W_be` | The number of workers per backend replica |
227+
| $M_{\text{total}}$ | Total memory usage |
228+
| $R_{\text{fe}}$ | The number of frontend replicas |
229+
| $M_{\text{fe}}$ | The memory usage of each frontend replica |
230+
| $P_{\text{be}}$ | The number of backend partitions |
231+
| $RF_{\text{be}}$ | Backend redundancy factor |
232+
| $M_{\text{be}}$ | The memory usage of each backend replica |
233+
| $W_{\text{be}}$ | The number of workers per backend replica |
231234

232-
For example if you select the *Medium* memory profile with two frontend replicas, two backend partitions, and a backend redundancy factor of two, the total memory usage per replica would be:
235+
For example if you choose the *Medium* memory profile, the profile has a frontend memory usage of 1.9 GB and backend memory usage of 1.5 GB. Assume that the broker configuration is 2 frontend replicas, 2 backend partitions, and a backend redundancy factor of 2. The total memory usage is:
233236

234-
`2 * 1.9GB + (2 * 2) * 1.5GB * 2 = 3.8GB + 12GB = 15.8GB.`
237+
*2 * 1.9 GB + (2 * 2) * 1.5 GB * 2* = 15.8 GB
235238

236-
In comparison, the *Tiny* memory profile with two frontend replicas, two backend partitions, and a backend redundancy factor of two, the total memory usage per replica would be:
239+
In comparison, the *Tiny* memory profile has a frontend memory usage of 1.9 GB and backend memory usage of 1.5 GB. If you assume the same broker configuration, the total memory usage is:
237240

238-
`2 * 99MB + (2 * 2) * 102MB * 2 = 198MB + 816MB = 1.014GB.`
241+
*2 * 99 MB + (2 * 2) * 102 MB * 2 = 198 MB + 816 MB* = 1.014 GB.
239242

240243
## Cardinality and Kubernetes resource limits
241244

0 commit comments

Comments
 (0)