← Back to the chapter · Next detail →
Technical detail · AMQP Frames: Storage and Throughput Calculations
Fleet broker configuration assumptions
These RabbitMQ values are example configuration inputs for the fleet. They are not sizing results or AMQP protocol defaults.
| Parameter | Value | Why |
|---|---|---|
vm_memory_high_watermark | 0.6 (of 16 GB) | Leave headroom for Erlang VM |
disk_free_limit | 5 GB | Prevent disk-full crashes |
channel_max | 128 | Per-connection channel limit; budget truck and consumer channels |
heartbeat | 30 sec | Detect dead cellular connections |
consumer_timeout | 60000 ms | Allow for mobile network delays |
queue_type | quorum | Replicated for archive durability |
The illustrative hardware is three broker nodes, each with 16 GB RAM, a 1 TB NVMe SSD and four CPU cores, supporting a three-replica quorum. Recalculate infrastructure cost separately. A channel limit applies per connection; it does not allocate 128 channels across the whole fleet.