-
Notifications
You must be signed in to change notification settings - Fork 121
fixed bench statements #895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
All failure modes: zero, negative, null, below thresholds. Comparing Benchmarks: Speedups from master/bench-cpu.yaml to pr/bench-cpu.yaml are displayed below. Thus, numbers > 1 represent increases in performance.
Warning: Exec time speedup for simulation is less than 0.9 - Case: 5eq_rk3_weno3_hllc
Error: Benchmarking failed since grind time speedup for simulation below acceptable threshold (<0.95) - Case: 5eq_rk3_weno3_hllc
Warning: Exec time speedup for post_process is less than 0.9 - Case: 5eq_rk3_weno3_hllc
Warning: Exec time speedup for pre_process is less than 0.9 - Case: hypo_hll
Warning: Exec time speedup for simulation is less than 0.9 - Case: hypo_hll
Warning: Exec time speedup for post_process is less than 0.9 - Case: hypo_hll
Warning: Exec time speedup for pre_process is less than 0.9 - Case: viscous_weno5_sgb_acoustic
Warning: Exec time speedup for simulation is less than 0.9 - Case: viscous_weno5_sgb_acoustic
Error: Benchmarking failed since grind time speedup for simulation below acceptable threshold (<0.95) - Case: viscous_weno5_sgb_acoustic
Warning: Exec time speedup for post_process is less than 0.9 - Case: viscous_weno5_sgb_acoustic
Warning: Exec time speedup for pre_process is less than 0.9 - Case: ibm
Warning: Exec time speedup for post_process is less than 0.9 - Case: ibm
Case Pre Process Simulation Post Process
─────────────────────────────────────────────────────────────────────────────────────
5eq_rk3_weno3_hllc Exec: 0.95 Exec: -0.00 & Grind: 0.00 Exec: 0.84
hypo_hll Exec: 0.75 Exec: 0.84 Exec: 0.21
viscous_weno5_sgb_acoustic Exec: 0.86 Exec: 0.00 & Grind: 0.00 Exec: 0.77
ibm Exec: 0.68 N/A Exec: 0.63
Error: Benchmarking failed
Terminated
|
|
will merge once the benchmark CI passes |
|
sounds good |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #895 +/- ##
=======================================
Coverage 45.78% 45.78%
=======================================
Files 68 68
Lines 18658 18658
Branches 2251 2251
=======================================
Hits 8543 8543
Misses 8757 8757
Partials 1358 1358 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Benchmark / Phoenix gpu failed to build master oddly. |
|
Genuinely baffling, I can't see what could have triggered the failure. I will submit a manual benchmark job on Phoenix right now and share the results tonight. |
|
Phoenix is having filesystem migration issues. |
Co-authored-by: Spencer Bryngelson <[email protected]>
Description
Fixed print statements to be more clear that the test failed due to mainly grind time not reaching the threshold.
expected output at failure.
