Benchmarks

Performance benchmarks for the Cruiser Carrier Board including network and storage.

Network Performance

The Cruiser’s 2.5GbE uplink port provides substantial throughput improvements over standard Gigabit Ethernet:

MetricResult
Peak Upload2.35 Gbps
Peak Download1.93 Gbps
Bidirectional Total3.2 Gbps
CPU Usage~27% (single core)

Test Configuration

Hardware

ComponentDetails
BoardCruiser Carrier Board
Compute ModuleRaspberry Pi Compute Module 5 Lite Rev 1.0
2.5GbE ControllerRealtek RTL8156BG (USB 3.0)
Test EndpointMacBook Pro with 2.5GbE USB dock
NetworkDirect connection via 2.5GbE switch

Software

ComponentVersion
OSDebian GNU/Linux 13 (trixie)
Kernel6.12.47+rpt-rpi-2712
iperf3 (Cruiser)3.18
iperf3 (Client)3.20

Both endpoints confirmed at 2500 Mb/s full-duplex before testing:

Speed: 2500Mb/s
Duplex: Full
Link detected: yes

Benchmark Results

All tests ran for 30 seconds using TCP with default settings.

Single Stream Performance

DirectionThroughputEfficiency
Upload (TX)2.35 Gbps94%
Download (RX)1.93 Gbps77%

Upload (client → Cruiser):

[ ID] Interval           Transfer     Bitrate
[  7]   0.00-30.01  sec  8.22 GBytes  2.35 Gbits/sec    sender
[  7]   0.00-30.01  sec  8.22 GBytes  2.35 Gbits/sec    receiver

Download (Cruiser → client):

[ ID] Interval           Transfer     Bitrate         Retr
[  7]   0.00-30.01  sec  6.75 GBytes  1.93 Gbits/sec    0    sender
[  7]   0.00-30.01  sec  6.75 GBytes  1.93 Gbits/sec         receiver

Multi-Stream Performance (4 Parallel)

DirectionThroughputvs Single Stream
Upload (TX)2.35 GbpsSame
Download (RX)1.93 GbpsSame

Multi-stream tests confirm the link is fully saturated with a single stream — additional parallel connections do not increase throughput.

Bidirectional Performance

Simultaneous upload and download:

DirectionThroughput
Upload (TX)2.34 Gbps
Download (RX)857 Mbps
Combined3.2 Gbps

When contending for the USB 3.0 bus, upload traffic is prioritized. The combined bidirectional throughput exceeds 3 Gbps.

CPU Utilization

During maximum throughput testing:

MetricValue
iperf3 process27% (single core)
System overhead~10% (kernel/softirq)
CPU idle90%

The 2.5GbE port leaves ample CPU headroom for other tasks.

Technical Notes

Why Download is Lower Than Upload

The 2.5GbE uplink port connects via USB 3.0, which has asymmetric performance characteristics. This is normal behavior for USB-based network adapters:

  • Upload (host → device): USB bulk OUT transfers are highly efficient
  • Download (device → host): USB bulk IN transfers have more protocol overhead

Despite this asymmetry, download throughput of 1.93 Gbps is still nearly double Gigabit Ethernet (1.0 Gbps).

Real-World Implications

For typical NVR/camera workloads where cameras upload footage to Cruiser:

  • Camera streams: Upload direction benefits from full 2.35 Gbps
  • Client viewing: Even reduced download speed (1.93 Gbps) vastly exceeds Gigabit
  • 8x cameras: Each 1GbE camera can stream at full speed without an uplink bottleneck

Reproduce These Tests

Install iperf3

On Cruiser:

sudo apt update && sudo apt install -y iperf3

On test client (macOS):

brew install iperf3

Run Tests

Start server on Cruiser:

iperf3 -s

Run from client:

# Single stream upload
iperf3 -c CRUISER_IP -t 30

# Single stream download
iperf3 -c CRUISER_IP -t 30 -R

# Multi-stream upload (4 parallel)
iperf3 -c CRUISER_IP -t 30 -P 4

# Multi-stream download
iperf3 -c CRUISER_IP -t 30 -P 4 -R

# Bidirectional
iperf3 -c CRUISER_IP -t 30 --bidir

Check link negotiation before testing:

# On Cruiser (eth1 is typically the 2.5GbE interface)
/usr/sbin/ethtool eth1 | grep Speed

Expected output: Speed: 2500Mb/s

Storage Performance

The Cruiser’s JMS561 SATA controller provides dual-port storage via USB 3.0:

MetricSingle DriveDual Drive (Simultaneous)
Sequential Read168 MiB/s318 MiB/s
Sequential Write163 MiB/s301 MiB/s
Random 4K Read90 IOPS—
Random 4K Write376 IOPS—
CPU Usage~2% system~2% system

Storage Test Configuration

ComponentDetails
SATA ControllerJMicron JMS561 (USB 3.0 bridge, 2-port)
Test Drives2x WD Purple 2TB (WDC WD22PURZ-74B4ZY0)
Drive Type5400 RPM surveillance HDD
RAID ModeJBOD (independent drives)
Benchmark Toolfio 3.39

Sequential Performance

Both SATA ports deliver full HDD throughput. The JMS561 USB 3.0 interface (5 Gbps theoretical) does not bottleneck these drives.

Single drive:

Sequential Read:  168 MiB/s (176 MB/s)
Sequential Write: 163 MiB/s (171 MB/s)

Dual drive simultaneous I/O:

Sequential Read:  318 MiB/s (333 MB/s) — nearly 2x single drive
Sequential Write: 301 MiB/s (315 MB/s) — nearly 2x single drive

Both drives can operate at full speed simultaneously, confirming no controller bottleneck.

Random I/O Performance

Random 4K performance is HDD-limited (seek time), not interface-limited:

TestIOPSLatency
Random 4K Read (QD=1)9011ms
Random 4K Read (QD=32)90—
Random 4K Write (QD=1)376—

Higher queue depth does not improve random read IOPS on HDDs — the mechanical seek time is the bottleneck. Random writes benefit from drive write caching.

RAID Modes

The JMS561 supports hardware RAID with four modes:

ModeCapacityDescriptionUse Case
JBOD2x individualIndependent drivesMaximum flexibility
RAID 0Combined (2x)Striping across drivesMaximum throughput
RAID 1Single driveMirroring for redundancyData protection
SPANCombined (2x)ConcatenationSingle large volume

RAID Mode Performance Comparison

Benchmarked with 2x WD Purple 2TB HDDs (5400 RPM):

TestSingle DriveBoth Drives (Parallel)RAID 0RAID 1
Sequential Read168 MiB/s318 MiB/s316 MiB/s168 MiB/s
Sequential Write163 MiB/s301 MiB/s311 MiB/s158 MiB/s
Random 4K Read90 IOPS—112 IOPS119 IOPS
Random 4K Write376 IOPS—149 IOPS367 IOPS

“Both Drives (Parallel)” = JBOD mode with simultaneous I/O to both drives, simulating NVR workload (record + playback).

Key observations:

  • RAID 0 nearly doubles sequential throughput (316/311 MiB/s vs 168/163 MiB/s single drive)
  • RAID 0 random write IOPS drops significantly due to striping overhead on HDDs
  • RAID 1 read performance equals single drive (no read striping in this controller)
  • RAID 1 write performance slightly lower (writes go to both drives)
  • Both drives in parallel achieves similar throughput to RAID 0 with more flexibility

Recommendations:

WorkloadRecommended ModeReason
Surveillance NVRJBODFlexibility for separate record/playback
Maximum write speedRAID 0~2x sequential throughput
Critical dataRAID 1Automatic redundancy
Single large volumeSPANSimple combined capacity

Hardware vs Software RAID Performance

Comparing the JMS561 hardware RAID against Linux mdadm software RAID:

RAID 0 (Striping):

TestHardware (JMS561)Software (mdadm)Difference
Sequential Read316 MiB/s314 MiB/s~same
Sequential Write311 MiB/s302 MiB/s~same
Random 4K Read112 IOPS141 IOPSmdadm +26%
Random 4K Write149 IOPS816 IOPSmdadm +5.5x

RAID 1 (Mirror):

TestHardware (JMS561)Software (mdadm)Difference
Sequential Read168 MiB/s162 MiB/s~same
Sequential Write158 MiB/s155 MiB/s~same
Random 4K Read119 IOPS121 IOPS~same
Random 4K Write367 IOPS394 IOPSmdadm +7%

Key findings:

  • Sequential throughput is identical — both are limited by USB 3.0 and drive speed
  • Random IOPS significantly better with mdadm — especially RAID 0 writes (5.5x improvement)
  • Hardware RAID’s striping overhead hurts small writes — the JMS561 adds latency for random I/O
  • mdadm CPU usage is minimal — measured 3-5% during heavy writes (CM5 quad-core handles it easily)

See Software - Hardware vs Software RAID for a full comparison of when to use each approach.

SSD vs HDD Comparison

Testing with Samsung 870 EVO SSDs reveals the USB 3.0 interface limits:

TestHDD (5400 RPM)SSD (870 EVO)Bottleneck
Sequential Read168 MiB/s338 MiB/sDrive (HDD) / USB (SSD)
Sequential Write163 MiB/s314 MiB/sDrive (HDD) / USB (SSD)
Dual Drive Read318 MiB/s345 MiB/sDrive (HDD) / USB (SSD)
Dual Drive Write301 MiB/s317 MiB/sDrive (HDD) / USB (SSD)
Random 4K Read90 IOPS4,450 IOPSDrive (HDD) / USB (SSD)
Random 4K Write376 IOPS6,198 IOPSDrive (HDD) / USB (SSD)

Key findings:

  • USB 3.0 ceiling: ~340-350 MiB/s — a single SSD saturates the interface
  • Dual SSDs gain almost nothing — bandwidth is shared, not doubled
  • HDDs are drive-limited — USB 3.0 has headroom for 2x HDDs at full speed
  • Random IOPS improved 16-49x with SSDs despite USB protocol overhead

For surveillance workloads, HDDs are the better choice:

  • 5400 RPM drives fully utilize available bandwidth
  • Lower cost per TB
  • Better suited for continuous 24/7 streaming writes
  • SSDs provide no sequential throughput benefit with dual drives

Real-World Implications

For NVR/surveillance workloads:

  • 8x 1080p cameras @ 8Mbps: 8 MB/s total — easily handled by single drive
  • Recording + playback: Dual drives in JBOD allow separate record/playback operations
  • RAID 1 mirroring: Protects against single drive failure with no performance penalty for writes

Reproduce Storage Tests

Install fio:

sudo apt update && sudo apt install -y fio

Run benchmarks:

# Sequential write (1M blocks, 60 seconds)
sudo fio --name=seq_write --filename=/dev/sda --direct=1 --rw=write \
    --bs=1M --size=4G --numjobs=1 --runtime=60 --time_based --group_reporting

# Sequential read
sudo fio --name=seq_read --filename=/dev/sda --direct=1 --rw=read \
    --bs=1M --size=4G --numjobs=1 --runtime=60 --time_based --group_reporting

# Random 4K read
sudo fio --name=rand_read --filename=/dev/sda --direct=1 --rw=randread \
    --bs=4k --size=1G --numjobs=1 --iodepth=1 --runtime=60 --time_based --group_reporting

# Dual drive simultaneous read
sudo fio --name=dual_read --filename=/dev/sda:/dev/sdb --direct=1 --rw=read \
    --bs=1M --size=4G --numjobs=1 --runtime=60 --time_based --group_reporting

Test Date

Benchmarks performed: January-February 2026

Last modified October 23, 2026