
Tech
rekuiper 0.500: Moving the Engine Hot Path to RAM and Finding its Exact Physical Limits (up to 200k msg/s)
When we published our earlier benchmarks for rekuiper (our Rust reimplementation of LF Edge eKuiper for edge gateways and IoT hubs), the numbers answered our first question: on five real-world MQTT workloads, memory stayed bounded between 5 and 10 MB while Go-based engines climbed to hundreds of megabytes or failed.
In that test, rekuiper sustained 100,000 messages per second on a single pinned core . At offered 200,000 msg/s, however, it dropped packets or backlogged upstream.
Say...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to