Rust-based rekuiper uses 5–10 MB memory vs rivals' 1 GB in edge stream processing

I-Dacs Labs Engineering rebuilt LF Edge eKuiper as 'rekuiper' in Rust and benchmarked it against eKuiper, Telegraf, and Redpanda Connect across five real-world MQTT workloads on a single-core, 1 GB memory setup. The key finding was not peak throughput but memory efficiency: rekuiper held between 5 and 10 MB on windowed workloads, while Go-based engines consumed up to a full gigabyte or failed entirely. rekuiper matched eKuiper's REST API, SQL dialect, and CLI surface so existing rules and tooling require no changes. The engine uses bounded queues and a reserve-then-commit admission model to prevent data loss and backpressure buildup under bursty traffic typical of industrial edge deployments. Benchmarking also uncovered a correctness bug in rekuiper itself that a throughput-only test would have missed, highlighting the importance of message-by-message output verification.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in