Poisson solver, nightly: 2026-10-16: np4
← Poisson solver, nightly: 2026-10-16 · ‹ np2
Summary
Section titled “Summary”solve(in simulation) is the largest hotspot: 423 ms over 40 calls, 85.4% of the session.- The three largest hotspots account for 97% of the session.
Hotspots
Section titled “Hotspots”The leaves of the call tree with the most time: regions without nested regions, and the own time parents spend outside theirs. Shares are of the session. Click one to find it in the table.
Region statistics
Section titled “Region statistics”| region | % session | total [s] | trend | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| scope_profiler.session (4x) | 100.00% | 0.494608 | |||||||||||||||||||||||||||||||
| └─ (own) | 3.23% | 0.016000 | |||||||||||||||||||||||||||||||
Per rank
| |||||||||||||||||||||||||||||||||
| └─ simulation (4x) | 96.77% | 0.478608 | |||||||||||||||||||||||||||||||
| │ └─ (own) | 0.00% | 0.000000 | |||||||||||||||||||||||||||||||
Per rank
| |||||||||||||||||||||||||||||||||
| │ └─ setup (4x) | 3.23% | 0.016000 | |||||||||||||||||||||||||||||||
Per rank
| |||||||||||||||||||||||||||||||||
| │ └─ solve (40x) | 85.44% | 0.422608 | |||||||||||||||||||||||||||||||
Per rank
| |||||||||||||||||||||||||||||||||
| │ └─ exchange (40x) | 8.09% | 0.040000 | |||||||||||||||||||||||||||||||
Per rank
| |||||||||||||||||||||||||||||||||
| No regions match the filter. | |||||||||||||||||||||||||||||||||
Durations are in seconds. (own) rows show a region's time excluding its children. % session uses wall-clock coverage; overlapping recursive calls count once. Click a row for its call site and per-rank breakdown.
Load balance
Section titled “Load balance”Each region's own time per rank, excluding nested regions, so a parent does not repeat its children's imbalance. Excess is how much longer the slowest rank spends than the average rank: the most balancing that region could save. Regions are ordered by it.
| region | mean | min | max | slowest rank | imbalance | excess | min · mean · max |
|---|---|---|---|---|---|---|---|
| solve | 106 ms | 98.1 ms | 111 ms | 0 | +6% | 5.82 ms | |
| setup | 4 ms | 4 ms | 4 ms | 0 | +0% | 0 s | |
| exchange | 10 ms | 10 ms | 10 ms | 0 | +0% | 0 s |
Rank comparison
Section titled “Rank comparison”Each cell compares one rank's time in a region with the region's mean over the ranks. Rank 0, in red in the header, spends the most time in regions overall. Hover a cell for its time.
faster than the meanslower
| region | mean | 0 | 1 | 2 | 3 |
|---|---|---|---|---|---|
| solve | 106 ms | +5.5% | −7.2% | +3.5% | −1.8% |
| exchange | 10 ms | 0% | 0% | 0% | 0% |
| setup | 4 ms | 0% | 0% | 0% | 0% |
| all regions | 120 ms | +4.9% | −6.4% | +3.0% | −1.6% |
Charts
Section titled “Charts”Region durations
Each bar shows a region's total recorded duration, summed over the selected ranks, longest first.
Timeline: np4 (rank 0)
Each bar is one recorded region call on rank 0. Its position and width show when the call started and how long it ran; colors identify regions.
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.
Metadata
Section titled “Metadata”| execution | 2026-10-16 |
|---|---|
| date | 2026-10-16 |
| commit | d4e5f6a |
| chip_information | synthetic CPU |
| mpi_size | 4 |
| num_nodes | 1 |
| omp_num_threads | 1 |
| platform | synthetic |
| scope_profiler_version | sample |
| timestamp | 2026-10-17T12:00:00Z |
| total_cores | 4 |