RustMinerSystem

Documentation

RMS Protocol and Connection Compression

Compare RMS2, RMS3, RMS3(Zstd), and RMS3(NB), then configure compression level, super compression, and outbound connection count.

Compression Settings

RMS optimizes transport at two layers: protocol compression reduces public data volume, while connection consolidation reduces the number of outbound sessions. Tune both while monitoring traffic, CPU, latency, hashrate, and rejects.

Protocol Comparison

Protocol Use case Guidance
RMS3(NB) Extreme BTC/LTC traffic reduction BTC/LTC only; read the NB guide.
RMS3(Zstd) Balance compression and CPU Usually more CPU-friendly than RMS3.
RMS3 General high compression Start at a low or medium setting.
RMS2 Historical compatibility Connect to RMS2 server ports only.

The local and server listener protocols must be identical.

Compression Level and Super Compression

Higher compression normally reduces more traffic and increases CPU pressure. Keep protocol-specific settings synchronized where the interface requires it.

Recommended order:

  1. Establish a baseline with 1–5 miners.
  2. Verify protocol, coin, password, and remote address.
  3. Start at a low or medium compression level.
  4. Set the outbound connection count.
  5. Increase compression only after the baseline is stable.
  6. Change one variable at a time and record before/after metrics.

Outbound Connection Count

Fewer outbound connections provide stronger consolidation but may increase CPU, latency, and reject sensitivity. Use these only as starting points:

  • RMS3 or RMS3(Zstd): begin around 1 outbound connection per 100 miners.
  • RMS3(NB): for BTC/LTC-only ports, begin with 3–6 outbound connections per port.
  • Different coins and local ports create separate outbound groups.

Acceptance Criteria

During expansion, verify that RMS CPU and memory remain safe, inbound/outbound counts match the rollout, RustMinerSystem workers and hashrate remain normal, upstream latency and rejects do not rise unexpectedly, and public traffic falls as expected.

If CPU or rejects increase, lower compression, raise the outbound count, and then reduce the number of miners per RMS instance. Published compression ratios cannot be reproduced in every environment; production measurements are authoritative.