Limit Message Rate

Throttles {{type:t}} to a target rate by dropping messages. Useful when the downstream consumer is slower than upstream and back-pressure isn't acceptable.

How it fits

{{type:t}} -> {{component:limit_message_rate}} -> {{type:t}}

Typical backends

• High-FPS feed -> display-friendly UI: {{component:input_camera}} (60 fps) -> {{component:limit_message_rate}} ({{param:message_rate}}: 15) -> {{component:output_browser_stream}}.
• Throttled DB writes: sensor stream -> {{component:limit_message_rate}} ({{param:message_rate}}: 1) -> {{component:write_database_sqlite}}.
• API call rate cap: detection events -> {{component:limit_message_rate}} ({{param:message_rate}}: 0.5) -> {{component:output_json_http}}.

Caveats

• Drops messages — the data is lost, not delayed. Use a buffer/queue if delivery guarantees are needed.
• {{param:time_constant}} is a smoothing/responsiveness knob. Larger values smooth bursts at the cost of slower adaptation.
• The internal algorithm switches at 1 Hz: EMA above, token-bucket below. Behaviour around the boundary can change subtly.
• No content-based prioritisation; drops are timing-only.