This work presents a comprehensive benchmark evaluation of visual odometry (VO) and visual SLAM (VSLAM) systems for mobile robot navigation in real-world logistical environments. We compare multiple visual odometry approaches across controlled trajectories covering translational, rotational, and mixed motion patterns, as well as a large-scale production facility dataset spanning approximately 1.7 km. Performance is evaluated using Absolute Pose Error (APE) against ground truth from a Vicon motion capture system and a LiDAR-based SLAM reference. Our results show that a hybrid stack combining the cuVSLAM front-end with a custom SLAM back-end achieves the strongest mapping accuracy, motivating a deeper integration of cuVSLAM as the core VO component in our robotics stack. We further validate this integration by deploying and testing the cuVSLAM-based VO stack on an NVIDIA Jetson platform.
Figures & tables
Figure 1: VO trajectories (from left to right): L-shape, hybrid & rotation-heavy sequences.
Sequence
Linear Velocity (m/s)
Angular
Mean
Max
Mean Angular Vel. (deg/s)
Max Angular Acceleration (deg/s 2 )
L-shaped
0.53
2.05
6.44
16.69
Rotation-Heavy
0.31
1.00
29.33
37.80
Hybrid
0.42
2.76
25.35
39.28
Table 1: Trajectory motion statistics per VO sequence.
Method
L-shaped
Rotation-Heavy
Long Sequence
Avg. Inference
Max Inference
Avg. CPU
Max CPU
AVG GPU
Time (ms)
Time (ms)
Usage (%)
Usage (%)
Usage (%)
cuVSLAM
0.057±0.01
0.296±0.025
0.850±0.034
2.262
3.137
2.002
8.600
6.200
ORB-SLAM
0.103
0.392
0.974
21.828
30.074
4.759
11.500
−
RTAB-Map
0.10±0.02
0.390±0.14
1.37±0.406
35.033
45.354
3.573
7.200
−
Wheel Encoder
0.071
0.183
0.604
−
−
−
−
−
Table 2: APE (m) & Computational Costs results across scenarios. APE: Mean ± std over 10 runs (single run for ORB-SLAM and Wheel Encoder) on Desktop
Method
L-shaped
Rotation-Heavy
Long Sequence
Avg. Inference
Max Inference
Avg. CPU
Max CPU
AVG GPU
Time (ms)
Time (ms)
Usage (%)
Usage (%)
Usage (%)
cuVSLAM
0.067±0.05
0.301±0.12
0.640±0.43
9.400
40.340
9.601
61.011
5.300
ORB-SLAM
0.150
0.308
0.899
60.342
71.572
36.009
61.500
−
RTAB-Map
0.11±0.06
0.311±0.17
0.92±0.54
86.300
144.7
25.600
40.500
−
Wheel Encoder
0.071
0.183
0.604
−
−
−
−
−
Table 3: APE (m) & Computational Costs results across scenarios. APE: Mean ± std over 10 runs (single run for ORB-SLAM and Wheel Encoder) on Xavier
Figure 2: Radar plot comparing the metrics of each method across the three VO sequences. The wheel encoder baseline is included for reference. Smaller areas indicate better performance.
Method
Seq-570
Seq-1700
Tick-Rate (Hz)
Avg. CPU Usage (%)
Max CPU Usage (%)
Avg. GPU Usage (%)
Mean
Max
RMSE
Mean
Max
RMSE
cuVSLAM
0.32±0.25
1.27
0.41
1.57±1.25
5.21
2.01
105.3
9.10
33.00
65.00
Idealworks NVIDIA Hybrid
0.61±0.29
1.09
0.68
0.91±0.29
2.2
0.54
1.50
18.74
35.00
66.26
RTAB-Map
−
−
−
5.89±4.69
22.14
7.53
0.95
−
−
−
ORB-SLAM
0.34±0.22
1.61
0.38
1.17±1.16
5.19
1.65
12.50
52.28
79.00
−
Table 4: VSLAM APE (m) results on the deployment dataset on Xavier
Method
Large-Scale Support
Inference Time
Production Grade
Rank
Idealworks NVIDIA Hybrid
⊕ Post-run map management ⊕ Multi-session & multi-robot mapping support
⊕ GPU-accelerated pipeline powered by cuVSLAM ⊕ Consistent inference time with growing map size
⊕ Production-ready ⊕ Seamless ROS2 integration
1 st
cuVSLAM
⊕ Multi-camera support ⊕ Multi-modality support (IMU, RGB-D, Stereo) ⊖ No post-run map management tools
⊕ GPU-accelerated ⊕ High throughput from SLAM stack
⊕ Production-ready ⊕ ROS2 integration via Isaac ROS Visual SLAM
2 nd
RTAB-Map
⊕ Memory management system ⊕ Constant inference time on unbounded maps ⊕ Multi-robot & multi-session support
⊖ Dense stack, generally slower ⊖ Unstable odometry under rapid motion ∼ Inference time stable with map size
⊕ Near production-ready ∼ Moderate integration effort
3 rd
ORB-SLAM3
⊖ No large-map handling ⊖ No pure localization mode ⊖ No multi-session or multi-robot support
⊕ Fast map updates via multi-threading ⊖ Slow ORB feature extraction ⊖ Inference time degrades with map size
⊕ Competitive accuracy in industrial settings ⊖ Heavy development effort required ⊖ Limited production support
4 th
Table 5: Deployability comparison of VSLAM methods.
Figure 3: Idealworks NVIDIA hybrid estimated trajectory errors across both sequences.