Skip to content

Improve hotspot attribution diagnostics#83

Merged
arkerone merged 4 commits into
mainfrom
refactor/hotspot-attribution-cleanup
May 16, 2026
Merged

Improve hotspot attribution diagnostics#83
arkerone merged 4 commits into
mainfrom
refactor/hotspot-attribution-cleanup

Conversation

@arkerone
Copy link
Copy Markdown
Owner

Summary

  • Preserve anonymous user-code wrapper frames as actionable CPU attribution and agent read targets.
  • Propagate richer user-caller evidence across CPU, memory, async, and GC findings.
  • Clarify internal hotspot attribution naming across core, detectors, and CLI renderers.
  • Add a changeset for @lanterna-profiler/core, @lanterna-profiler/detectors, and @lanterna-profiler/cli.

Validation

  • npm run check
  • npm run typecheck
  • npm test
  • npm run pack:check
  • git diff --check

arkerone and others added 4 commits May 15, 2026 23:51
…s, harden cpu pattern attribution via source validation, recalibrate deopt-loop thresholds
When the V8 heap sampler runs without observing any allocation, the
memory profile silently looked healthy (confidence: high, no reasons).
Add an explicit quality reason + recommendation so consumers can tell
"capture vide" from a real signal — typical with idle workloads,
overly-short --duration, or scripts that only allocate off-heap
(Buffer.alloc, ArrayBuffer, native modules).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@arkerone arkerone merged commit 124f2c7 into main May 16, 2026
3 checks passed
@arkerone arkerone deleted the refactor/hotspot-attribution-cleanup branch May 16, 2026 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant