Draft: Stricter efficiency tests
- No more warnings for efficiency or run changes tests - it is either pass or fail
- The efficiency check will fail if any expected efficiency results are missing
- Efficiency artifacts are kept for 2 days, not 2 hours
Todo:
-
check efficiency test has the appropriate behaviour -
Rebase
closes #284 (closed), #301 (closed)
Merge request reports
Activity
assigned to @roneil
added 7 commits
-
d6587b4a...b120ab6c - 4 commits from branch
master
- 58cd7598 - Fail if we can't find efficiency results for a reference file
- 8311fd8b - don't fail efficiency or run changes tests with warnings in any case
- cd7a98f8 - use compgen; add a more helpful error
Toggle commit list-
d6587b4a...b120ab6c - 4 commits from branch
added 6 commits
-
cd7a98f8...946241a6 - 3 commits from branch
master
- bdacf0f3 - Fail if we can't find efficiency results for a reference file
- 532db4f0 - don't fail efficiency or run changes tests with warnings in any case
- 991051fb - use compgen; add a more helpful error
Toggle commit list-
cd7a98f8...946241a6 - 3 commits from branch
added only GitLab CI label
added 1 commit
- 93f1ece7 - keep artifacts longer in minimal pipeline for efficiency tests
I would suggest to have less reference files.
One possibility would be to have one reference file per TARGET_DEVICE, ie.
CPU
,CUDA
,HIP
.However, it may be the case that there are differences between various
CUDA
executions depending on the major / minor number. In fact we are producing several versions of the kernels with each compilation since we compile with-gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_75,code=compute_75 -gencode=arch=compute_86,code=compute_86
(note: this compilation is akin to the feature oficc
of compiling for several vector widths and choosing at runtime depending on CPUID). If that is the case, then I would suggest to have different reference files, one per execution path. That would mean:CPU
,HIP_908
(we only compile and have architecturegfx908
at the moment there),CUDA_70
,CUDA_75
,CUDA_86
.Edited by Daniel Hugo Campora Perez
added 2 commits
added 1 commit
- ce7ef52a - set up run_physics efficiency for HIP as done with run_throughput
After adding references for all devices, more efficiency variations uncovered, but it seems device-specific in this case: https://gitlab.cern.ch/lhcb/Allen/-/jobs/17778169#L167
Checking Upgrade_BsPhiPhi_MD_FTv4_DIGI_1k_hlt1_pp_validation_a6000.txt Folder : run_physics_efficiency_output_hlt1_pp_validation/ File : efficiency_Upgrade_BsPhiPhi_MD_FTv4_DIGI_1k_hlt1_pp_validation_a6000.txt Reference : test/reference/Upgrade_BsPhiPhi_MD_FTv4_DIGI_1k_hlt1_pp_validation_a6000.txt --- /builds/lhcb/Allen/test/reference/Upgrade_BsPhiPhi_MD_FTv4_DIGI_1k_hlt1_pp_validation_a6000.txt 2021-11-22 15:40:19.024000000 +0100 +++ efficiency_Upgrade_BsPhiPhi_MD_FTv4_DIGI_1k_hlt1_pp_validation_a6000.txt 2021-11-22 15:40:30.568000000 +0100 @@ -99,7 +99,7 @@ Events Candidates Hlt1KsToPiPi: 29 31 Hlt1TrackMVA: 196 297 -Hlt1TwoTrackMVA: 399 1079 +Hlt1TwoTrackMVA: 399 1078 Hlt1TwoTrackCatBoost: 369 897 Hlt1SingleHighPtMuon: 2 2 Hlt1LowPtMuon: 103 117 @@ -122,8 +122,8 @@ Hlt1Passthrough: 1000 0 Total decisions: 3134 -Total tracks: 1768 -Total SVs: 1380 -Total hits: 43758 -Total stdinfo: 22798 +Total tracks: 1767 +Total SVs: 1379 +Total hits: 43737 +Total stdinfo: 22786
added RTA label