In v0.500-beta, rekuiper’s author says the engine moved frequent catalog and metadata reads into memory while keeping SQLite for persistence. The author reports ceilings from 126,000 to 200,000 MQTT messages per second across five workloads, but those figures describe a one-core Docker/WSL2 test—not a measured limit for a production edge gateway. Two of the 200,000 msg/s results were bounded by the load generator, not by a demonstrated engine maximum.
What changed in rekuiper v0.500-beta
rekuiper is described by its author as a Rust reimplementation of LF Edge eKuiper for edge gateways and IoT hubs. In an article published September 21, 2026, project author Ankur Kumar Pandey says v0.500-beta changes where frequently accessed state lives during runtime: the stream, rule, and table catalog is loaded from SQLite into an in-memory catalog when the daemon starts.
As an Amazon Associate I earn from qualifying purchases.
Under the described design, runtime reads use in-memory maps. Mutations update memory first and are committed to SQLite asynchronously. The author also reports caching authentication public keys and configuration/schema material, sharing database connection pools, batching relational inserts, and raising actor queue depth from 1,024 to 32,768 records. These are implementation claims from the project author’s article; the consulted evidence does not independently verify them against source code or a separate review.
How the benchmark was run
The numbers below come from the author’s MQTT benchmark on a 12-core x86-64 host running Docker on WSL2 with cgroup v2. The rekuiper engine container was pinned to one CPU core, limited to 1 GiB of RAM with an equal amount of swap, and configured with one Tokio worker thread. Mosquitto ran in an isolated container on separate cores, with an outgoing queue limited to 4,096 messages or 1 MiB.
#1 Best Overall
- Multi-Protocol Support: Integrates with industrial systems and supports multiple communication protocols, including Modbus RTU/TCP, BACnet, OPC UA, OPC XML-DA, and IEC 104, enabling seamless connection with diverse industrial devices to meet different automation needs.
- Cloud Data Connectivity: Functions as an MQTT, HTTP, and Socket client, providing reliable data transmission and automatic reconnection to maintain continuous data flow for IoT applications.
- JS Script Programming Support: Offers flexibility through JavaScript scripting, allowing users to customize and extend the gateway's capabilities to meet specific application needs.
- Alarm and Event Management: Allows users to set trigger conditions, enabling event triggers and releases based on state transitions.
- Easy Configuration and Management: User-friendly graphical configuration software simplifies setup, allowing easy access to real-time and historical data through an HTTP server interface.
A standalone Rust tool, mqttgen, generated MQTT 3.1.1 QoS 0 traffic over eight connections. The article says the results were checked message by message for total counts, unique IDs, per-device aggregates, and exceptions.
The author describes a stepped rate search: 10,000 msg/s increments to find a range, followed by 2,500 msg/s and then 1,000 msg/s increments. A passing run required bounded queues, a bounded source gap at send completion, no more than 4,096 messages of backlog, and a post-send drain within five seconds. The article calls runs meeting this protocol “certified”; that term refers to the author’s stated test criteria, not external certification.
Rank #2
- This is an RS232/485 device data acquisitor / IoT gateway designed for industrial environment. It combines multi functions in one, including serial server, Modbus gateway, MQTT gateway, serial port to HTTPD Client, etc
- With RS232, RS485, WIFI and Ethernet interfaces, the module can realize functions such as serial port to WIFI, serial port to Ethernet, Ethernet to WIFI and so on. Support Screw Terminal and DC 5.5 Power Port for Power Supply, DC 6~36V Wide Voltage Range Input
- Support transparent transmission mode: Support TCP Server, TCP Client, UDP Server, UDP Client
- Support multi wireless networking methods: Support AP mode, STA mode, and AP+STA mode. Support multi wired networking methods: Support APLAN, APWAN, Router, and Bridge mode
- Multi Configuration Methods: Supports muliti configuration methods such as hosts, Web Browser and serial port Configuration. AT Command Mode: The user can query the current status of the module or set related parameters by sending AT commands
Five reported workload ceilings
All measurements in this table are claims in Pandey’s 2026 article for the test setup above. “RAM at ceiling” is the memory figure the author reports at that workload’s stated ceiling; it is not a like-for-like comparison at a shared throughput.
| Workload | Reported ceiling | What happened at the next tested rate | Reported RAM at ceiling |
|---|---|---|---|
| Telemetry JSON filter, 1,000 devices | 150,000 msg/s | At 151,000 msg/s, CPU reached 99.4% and the broker reportedly dropped 20.53% of messages. | 17.4 MB |
| 10-second per-device windows, 1,000 devices | 200,000 msg/s certified on schedule | Above 200,000 msg/s, the generator schedule fell behind. The author says the engine remained lossless to 240,000 msg/s. | 6.7 MB |
| ESPHome topic routing, 10,000 topics | 150,000 msg/s | At 151,000 msg/s, CPU reached 99.3% and the broker reportedly dropped 5.05% of messages. | 16.6 MB |
| Vehicle wildcard windows, 10,000 VIN topics | 200,000 msg/s certified | The generator schedule fell behind at 210,000 msg/s. The author says the engine remained lossless to 220,000 msg/s. | 18.1 MB |
| EV charger session windows, 2,000 chargers | 126,000 msg/s | At 127,000 msg/s, session-close lag reached 16 seconds, exceeding the article’s five-second stability limit. | 6.0 MB |
How to interpret the limits
Some ceilings are failure boundaries; others are test boundaries
For the telemetry filter and ESPHome routing workloads, the next tested rate after 150,000 msg/s coincided with near-saturated CPU and reported broker loss. For EV charger sessions, the limiting condition was delayed session closure: 16 seconds of lag at 127,000 msg/s against a five-second pass threshold. Those are different failure modes, so the three figures should not be treated as equivalent kinds of “maximum.”
Rank #3
- NO SUBSCRIPTION FEES & PRIVATE LORAWAN NETWORK: Build a local LoRaWAN IoT network with the built-in SIoT server and pre-installed Node-RED. Collect data, create dashboards, and run automation flows locally without required cloud service fees. Suitable for DIY makers, home gardeners, educators, and small IoT prototype projects.
- LOCAL DATA PROCESSING & PRIVACY CONTROL: Sensor data can be processed on the local network through the built‑in MQTT/SIoT server, reducing reliance on third‑party cloud platforms. Local automation rules continue running when internet access is unavailable — suitable for home, garden, greenhouse, and classroom IoT setups.
- 4KM COVERAGE & 8-CHANNEL RELIABILITY: Equipped with the SX1302 8-channel LoRaWAN chip, -140dBm sensitivity, 27dBm max transmit power, and included 5dBi antenna. Supports up to 4km coverage in open environments, helping connect garden sensors, greenhouse nodes, garages, mailboxes, and remote monitoring points.
- NODE-RED DRAG-AND-DROP VISUAL AUTOMATION：Automation rules, data dashboards, and control logic can be built with little to no coding using the pre‑installed Node‑RED. Flows such as reading soil moisture, checking temperature, and sending relay commands are created through a visual interface — reducing setup time for maker, education, and prototype projects.
- EASY SETUP WITH WIFI AP & MQTT INTEGRATION: Configure the gateway via Wi-Fi AP mode using a laptop or mobile device. Built-in MQTT broker supports integration with Node-RED dashboards, and other MQTT-compatible platforms. Designed for indoor residential, educational, and prototyping use; not intended for outdoor installation.
For per-device windows and vehicle wildcard windows, 200,000 msg/s was the highest rate the article calls certified on schedule. The author attributes the next-rate boundary to the generator falling behind, while reporting lossless engine operation at higher rates—240,000 msg/s for the per-device window case and 220,000 msg/s for vehicle windows. Those higher figures are not certified on-schedule ceilings, and neither scenario establishes the engine’s absolute maximum.
One host core is not a gateway result
The test pins the engine to one core on an x86-64 host under Docker/WSL2; it does not measure a named industrial gateway or Raspberry Pi-class device. The reported rates therefore do not establish what rekuiper will sustain on hardware with different processors, storage, memory, operating systems, network paths, payloads, or sinks. They also do not establish sustained production throughput under a different broker configuration or traffic pattern.
Rank #4
- High-Performance LoRaWAN Gateway with Advanced Chipset: Powered by MT7628 MCU and SX1303 + SX1250 chipset, the HT-M7603 delivers robust 8-channel uplink & 1-channel downlink LoRa communication. Supports LoRaWAN 1.0.2 Class A/C protocols, with up to +27dBm max TX power and exceptional -139dBm RX sensitivity, ensuring stable long-range signal transmission and reliable IoT device connectivity.
- Dual Network Connectivity & Flexible Deployment: Features integrated Wi-Fi (IEEE 802.11 b/g/n 2.4GHz) and 10/100M Ethernet ports for versatile network access. Compact, sleek wall-mount design enables easy installation anywhere indoors, ideal for standalone use or signal blind-zone filling in smart homes, offices, and commercial buildings.
- User-Friendly Web UI & Effortless Configuration: Intuitive web-based management interface allows quick setup via device Wi-Fi. Supports seamless connection to mainstream LoRa servers (TTN, ChirpStack, AWS IoT Core) and flexible network parameter customization. OTA firmware update capability simplifies maintenance and keeps the gateway optimized.
- Wide Compatibility & Versatile IoT Applications: Works with 915MHz frequency bands to meet global regional standards. Perfect for diverse IoT scenarios including smart agriculture, environmental monitoring, asset tracking, industrial automation, and smart building control. Low-power 5V USB-C power supply ensures energy-efficient 24/7 operation.
- Premium Build & Reliable Long-Term Performance: Constructed with high-quality components for durability, operating stably in -20°C to 70°C temperatures and 10%-90% non-condensing humidity. Cost-effective indoor solution with strong anti-interference performance, delivering consistent performance for large-scale IoT network deployments.
Cross-engine comparisons need matched conditions
A message-rate comparison is meaningful only when the workloads and constraints align. At minimum, compare message format and parsing, device/topic count, window type, MQTT QoS, CPU pinning and worker count, memory and swap limits, broker queue bounds, generator scheduling, loss accounting, and post-send drain criteria. Compare memory at the same workload and throughput: the author also gives a separate memory comparison at 20,000 msg/s, which should not be conflated with the RAM figures at each workload’s ceiling. The article’s multi-engine comparison remains author-reported rather than an independent head-to-head replication.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What is available for trying or reproducing it
The author says rekuiper is free and open source under the MIT and Apache-2.0 licenses. The article points readers to the project repository, v0.500-beta releases, a Docker image, raw benchmark evidence, the mqttgen and iotrunner harnesses, and reproduction instructions under test/benchmark/iiot-mqtt/. The described benchmark does not require a particular physical product; its host is identified only generically as a 12-core x86-64 system.
Best Value
- Powerful Edge Computing Capabilities: 1000 points+data acquisition+analysis
- Multiple Interface: Ethernet+2*RS485
- Protocol Conversion: Modbus to MQTT+Json, DL645 to MQTT+Json
- Rich Communication Protocol: MQTT/TCP
- Data Encryption: TCP+SSL, MQTT+SSL SD Card for Data Storage：To ensure data integrity
The results remain author-reported. The cited article does not establish that an independent organization reproduced the runs or that the measurements transfer to production gateway hardware.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
