📈 Profiling Analysis
Performance regression analysis comparing current profiling data to the baseline version.
Comparing baseline 0.244.10 to current 0.244.25
Performance Change Summary
| Metric | Value | Interpretation |
|---|---|---|
| Total Change | -1.4% | Overall performance vs baseline 0.244.10 |
| Concentration | 8.7% | Change concentrated in top 3 functions |
| Type | diffuse | Distribution pattern of changes |
What This Means
This analysis compares profiling data from baseline 0.244.10 to current 0.244.25 to identify which functions changed and by how much.
- Focused: Most change concentrated in 1–2 specific functions (easier to optimize)
- Mixed: Changes distributed across several functions
- Diffuse: Changes spread across many functions or systemic (harder to address)
- No Change: No significant performance difference detected
Top Contributors
Functions contributing most to performance changes from baseline 0.244.10 to current 0.244.25:
See the Differential flamegraphs for a visual breakdown of which call paths changed between versions.
Aggregate Flamegraphs
- Deploy Aggregate — combined view of all deploy benchmarks
- Validate Aggregate — combined view of all validate benchmarks
- Atomic Aggregate — atomic deployment operations
- Help Aggregate — help command startup and parsing
Methodology
Profiling data collected using Linux perf record --call-graph=fp at 18,181 Hz sample rate
with -C force-frame-pointers=yes on the profiling binary. Frame-pointer mode relies on
Fedora's frame-pointer-enabled glibc to produce complete call stacks through library code.
Flamegraphs generated using inferno-flamegraph with
Rust symbols demangled via rustfilt to preserve full crate paths.