Benchmarks · October 2026

Pull the plug and keep the recording.

We cut the power on a recording robot ten times. The Insaion Agent never lost more than 2 seconds. ros2 bag record lost about half a minute every time.

Insaion Agent0.9s
ros2 bag record32.6s

Seconds of recording lost in a typical power cut. Lower is better.

37x less data lost

Each dot is one power cut at a random moment. The line marks the median.

Insaion Agentmedian 0.88 s · worst 1.95 s
ros2 bag recordmedian 32.6 s · worst 35.0 s

Made for bad networks

Robots live on cellular and patchy Wi-Fi. We tested for it.

24h+

offline, and live telemetry still arrives

It waits on the robot's disk and reaches the cloud within seconds of the link coming back.

128kbit/s

is enough for live telemetry

Slower than old 2G data, with 5% packet loss. Over 99.9% arrived.

1GB

recording uploaded over a patchy 2 Mbit/s link

Through two outages and a crash, with only 2% sent twice.

23s

for an urgent clip to jump the queue

Urgent uploads go first. A 1.7 GB upload already running steps aside, then picks up where it left off.

Uploads that follow the link

A 755 MB upload while the signal drops to 256 kbit/s, cuts out and comes back. It slows down, waits and speeds up again on its own, and 100% of live telemetry still arrives.

Link speedInsaion Agent upload
100 kbit/s1 Mbit/s10 Mbit/s

The same data, nothing dropped

Both recorders stored what the robot published, within 1%.

Insaion Agentros2 bag record
Heavy recording
13.75 GB
13.78 GB
Typical AMR
4.05 GB
4.07 GB
Drone flight (real bag)
0.51 GB
0.50 GB
Camera robot (real bag)
5.86 GB
5.80 GB

What it costs

On a typical AMR. ros2 bag record only records. The Insaion Agent also streams live telemetry and runs its own storage, so it uses a bit more CPU.

Insaion Agentros2 bag record

CPU, % of one core

PC
6.6 %
4.1 %
Raspberry Pi 4
34.7 %
21.7 %

Memory

PC
126 MB
177 MB
Raspberry Pi 4
136 MB
140 MB

How we tested

The robot
A typical AMR: IMU, odometry, TF, a camera, a lidar and 20 metrics. We also replayed real robot and drone recordings.
The rival
Stock ros2 bag record writing MCAP with the same compression and file split as the Insaion Agent.
Power cuts
An Ubuntu 24.04 machine on ext4, hard reset with nothing flushed, 30 to 90 s into the recording. Ten cuts each, read back after reboot.
Networks
Day-long outages, slow and lossy links and modem-sized buffers, shaped with Linux traffic control, against a local cloud that counts what arrives.
Hardware
A Ryzen 7 7800X3D PC, and a Raspberry Pi 4 with an SD card at half the sensor rate.
Version
Insaion Agent 1.0.0 on ROS 2 Jazzy.

Questions

Why does ros2 bag record lose so much in a power cut?

It writes through the operating system's cache and leaves flushing to the kernel, so the last half minute or so is still in memory when power goes. The Insaion Agent seals its recording about once a second and stores it durably, so a power cut costs about a second.

Does the Insaion Agent use more CPU than ros2 bag record?

A little. ros2 bag record only records. The Insaion Agent also streams live telemetry, runs its own storage engine and handles uploads. On a typical robot that is about 2.5% of one core more on a PC, and about 13% more on a Raspberry Pi 4.

Do I need to change my ROS 2 code to get these results?

No. The Insaion Agent discovers your ROS 2 topics by itself. There is no SDK and no code to change.

See it on your own robot

One install. The agent finds your ROS 2 topics by itself, with no SDK and no code changes.