Achieving a 155× speedup in a LiDAR data processing pipeline
| dc.contributor.author | Felix, Simon | |
| dc.contributor.author | Stutz, Manuel | |
| dc.contributor.author | Hartmann, Julia | |
| dc.contributor.author | Bächtiger, Yves | |
| dc.contributor.author | Timmel, Vincenzo | |
| dc.contributor.author | Wassmer, Andreas | |
| dc.contributor.author | Schramka, Filip | |
| dc.contributor.author | Strobach, Elmar | |
| dc.contributor.author | Leckebusch, Jürg | |
| dc.contributor.author | Angst, Christian | |
| dc.date.accessioned | 2026-09-17T10:50:12Z | |
| dc.date.issued | 2026 | |
| dc.description.abstract | Real-world data processing pipelines often grow incrementally over years and accumulate inefficiencies that no single processing step explains. We present a measurement-driven case study of optimizing one such system end-to-end: a multi-stage pipeline for high-resolution LiDAR road condition assessment. The original system required weeks of computation for a typical measurement campaign covering a 10 km road network and approximately 200GB of raw data. Our primary contribution is a continuous, measurement-driven optimization methodology. Automated per-commit benchmarks on fixed reference datasets track per-stage runtime throughout the project. This revealed that the dominant bottleneck shifted repeatedly as optimization proceeded. It allowed us to target each successive bottleneck and detect regressions early. Guided by this methodology, we consolidated a distributed eight-server architecture onto a single high-performance node, eliminated intermediate file I/O through in-memory stream processing, migrated heterogeneous runtimes (MATLAB, Python, C++) to a single managed C# codebase, and applied pervasive SIMD vectorization and parallelization. We achieved a 155× end-to-end speedup, enabling the pipeline to process data faster than it is recorded. We decompose this speedup per stage and estimate that software and architectural changes, rather than hardware alone, account for at least an order of magnitude of it. We also observe that carefully vectorized managed code matched or exceeded the original native code implementations for our workload.We do not claim novel algorithms, but contribute a reproducible methodology and quantitative evidence that disciplined engineering can yield order-of-magnitude improvements in legacy data processing systems. | |
| dc.identifier.doi | 10.1109/access.2026.3732940 | |
| dc.identifier.issn | 2169-3536 | |
| dc.identifier.uri | https://irf.fhnw.ch/handle/11645/58091 | |
| dc.identifier.uri | https://doi.org/10.26041/fhnw-17296 | |
| dc.language.iso | en | |
| dc.publisher | IEEE | |
| dc.relation.ispartof | IEEE Access | |
| dc.rights.uri | https://creativecommons.org/licenses/by/4.0/ | |
| dc.subject.ddc | 005 - Computer Programmierung, Programme und Daten | |
| dc.title | Achieving a 155× speedup in a LiDAR data processing pipeline | |
| dc.type | 01A - Beitrag in wissenschaftlicher Zeitschrift | |
| dc.volume | 11 | |
| dspace.entity.type | Publication | |
| fhnw.InventedHere | Yes | |
| fhnw.ReviewType | peer-reviewed | |
| fhnw.openAccessCategory | Gold | |
| fhnw.publicationState | Published | |
| fhnw.targetcollection | b508cce9-5084-49ae-a565-d8e5c348c3ab | |
| relation.isAuthorOfPublication | 024c053f-dd21-426d-8bc9-6706bcbbade8 | |
| relation.isAuthorOfPublication | 7bc3e302-9b5e-4a73-a77c-63173a0cfb86 | |
| relation.isAuthorOfPublication | c23b2446-36c7-4dc7-803b-c772801721a8 | |
| relation.isAuthorOfPublication | b1ec2cfc-09eb-433e-8139-0df20f30b4ac | |
| relation.isAuthorOfPublication | 65a8fc7a-89a6-4c96-aab4-1b4516821316 | |
| relation.isAuthorOfPublication | 87b55d3a-80bb-4449-b979-5f3f13ef1cf3 | |
| relation.isAuthorOfPublication | f05de49b-4ddc-43a0-8cc7-e67bad8c4061 | |
| relation.isAuthorOfPublication.latestForDiscovery | 024c053f-dd21-426d-8bc9-6706bcbbade8 |
Dateien
Originalbündel
1 - 1 von 1
Lade...
- Name:
- Achieving_a_155_Speedup_in_a_LiDAR_Data_Processing_Pipeline.pdf
- Größe:
- 14.18 MB
- Format:
- Adobe Portable Document Format
Lizenzbündel
1 - 1 von 1
Lade...
- Name:
- license.txt
- Größe:
- 2.66 KB
- Format:
- Item-specific license agreed upon to submission
- Beschreibung: