Asynchronous Thrust, main branch (2025.02.05.)

[krasznaa]

As a follow-up to #835, I wanted to see if I could simplify the code in question a little.

I couldn't quite do that, but I did stumble across another thing. That we were not letting Thrust run asynchronously so far. With this simple update, with the command:

traccc_throughput_mt_cuda --detector-file=geometries/odd/odd-detray_geometry_detray.json \
   --material-file=geometries/odd/odd-detray_material_detray.json \
   --grid-file=geometries/odd/odd-detray_surface_grids_detray.json \
   --use-detray-detector --digitization-file=geometries/odd/odd-digi-geometric-config.json \
   --use-acts-geom-source \
   --input-directory=/data/Acts/odd-simulations-20240509/geant4_ttbar_mu140/ \
   --input-events=100 --processed-events=200 --cpu-threads=2

, we go from:

Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Warm-up processing [==================================================] 100% [00m:00s]                                            
Event processing   [==================================================] 100% [00m:00s]                                            
Reconstructed track parameters: 11241101
Time totals:
                  File reading  2850 ms
            Warm-up processing  2101 ms
              Event processing  43079 ms
Throughput:
            Warm-up processing  210.183 ms/event, 4.75775 events/s
              Event processing  215.399 ms/event, 4.64254 events/s

to:

Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Using CUDA device: NVIDIA RTX A5000 [id: 0, bus: 1, device: 0]
Warm-up processing [==================================================] 100% [00m:00s]                                            
Event processing   [==================================================] 100% [00m:00s]                                            
Reconstructed track parameters: 10704497
Time totals:
                  File reading  2587 ms
            Warm-up processing  2013 ms
              Event processing  41526 ms
Throughput:
            Warm-up processing  201.325 ms/event, 4.96709 events/s
              Event processing  207.631 ms/event, 4.81624 events/s

Small, but any performance improvement is good...

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[stephenswat]

That's a nice find!

[stephenswat]

Out of curiosity, where does that 4.5 Hz figure come from? That's even slower than I was expecting. :(