Skip to content
Projects

Poisson solver, nightly: 2026-10-15: np2

all 5all levels

np2.h52026-10-17 12:00 UTCsynthetic CPU2 ranks5 regions0.211577 s profiled

← Poisson solver, nightly: 2026-10-15 · ‹ np1 · np4 ›

Wall time212 mssetup to finalize
Ranks2
Regions5
In regions98%of the session
Top hotspotsolve93.8% of the session
Load imbalance+1%solve, slowest on rank 0
  • solve (in simulation) is the largest hotspot: 393 ms over 20 calls, 93.8% of the session.
  • The three largest hotspots account for 98% of the session.

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% sessiontotal [s]trend
└─ (own) 1.91% 0.008000
│ └─ (own) 0.00% 0.000000

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.

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.

regionmeanminmaxslowest rankimbalanceexcessmin · mean · max
solve196 ms194 ms199 ms0+1%2.29 ms
setup4 ms4 ms4 ms0+0%0 s
exchange5 ms5 ms5 ms0+0%0 s

Each cell compares one rank's time in a region with the region's mean over the ranks. Every rank spends about the same time in regions overall, so the differences above are ranks waiting for each other. Hover a cell for its time.

faster than the meanslower

regionmean01
solve196 ms+1.2%−1.2%
exchange5 ms0%0%
setup4 ms0%0%
all regions205 ms+1.1%−1.1%
Region durations

Each bar shows a region's total recorded duration, summed over the selected ranks, longest first.

Timeline: np2 (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.

execution2026-10-15
date2026-10-15
commitc3d4e5f
chip_informationsynthetic CPU
mpi_size2
num_nodes1
omp_num_threads1
platformsynthetic
scope_profiler_versionsample
timestamp2026-10-17T12:00:00Z
total_cores2