Poisson solver, nightly: 2026-10-13
The strong-scaling study above, run every evening; the case page is the latest night.
Tags: cpu, nightly
Executions
Section titled “Executions”| date | details | runs |
|---|---|---|
| 2026-10-17 latest | commit: e5f6a7b | 3 |
| 2026-10-16 | commit: d4e5f6a | 3 |
| 2026-10-15 | commit: c3d4e5f | 3 |
| 2026-10-14 | commit: b2c3d4e | 3 |
| 2026-10-13 | commit: a1b2c3d | 3 |
This page shows 2026-10-13; the others are linked above.
| run | file | recorded | ranks | wall time | vs baseline | page |
|---|---|---|---|---|---|---|
| np1 | np1.h5 | 2026-10-17 12:00 UTC | 1 | 390 ms | baseline | run page |
| np2 | np2.h5 | 2026-10-17 12:00 UTC | 2 | 214 ms | −45.2% | run page |
| np4 | np4.h5 | 2026-10-17 12:00 UTC | 4 | 124 ms | −68.1% | run page |
Each run's page is linked on the right.
What changed
Section titled “What changed”Durations
Section titled “Durations”Charts
Section titled “Charts”Region durations
Grouped bars compare each region's mean call duration across the profiled runs.
Speedup
Each line is one region's speedup: its mean call duration on the run with the fewest MPI ranks divided by its mean call duration on each run. The dashed line is ideal scaling; a region below it gains less than its extra MPI ranks would allow. The 8 regions with the most time on that first run are shown. Valid for a strong-scaling study: the same total problem size on every run.
Rank imbalance
Each line compares a region's total duration by rank; its dashed line marks the mean across ranks. Points far from the mean identify stragglers.
Rank heatmap
This heatmap uses exclusive timings. Exclusive duration is the time spent in a region itself, excluding time spent in nested child regions; this prevents the enclosing session region from dominating the heatmap.
Executions over time
The wall time of each run in every execution of this case.
Metadata
Section titled “Metadata”| execution | 2026-10-13 |
|---|---|
| date | 2026-10-13 |
| commit | a1b2c3d |