startup-perf

What problem does it solve?

It solves the problem of not knowing where time is spent when Aspire applications start, making regressions hard to detect and performance investigations slow.

Core Features & Use Cases

• Captures end-to-end startup traces: Uses Aspire’s hidden CLI self-profile flow to collect OTEL traces from the CLI, the AppHost hosting layer, and (when applicable) DCP startup telemetry.
• Exports a reusable trace artifact: Produces a zip containing an OTLP JSON trace export you can inspect and compare before/after changes.
• Separates profiling from reported telemetry: Ensures profiling spans and high-cardinality profiling identifiers do not contaminate production telemetry by design.
• Use cases: Investigate startup slowdowns, validate performance-impacting changes in AppHost code, and compare baseline vs. feature branch startup behavior with correlated spans.

Quick Start

Run an Aspire command with the hidden capture flag and write the exported trace zip to artifacts/tmp/startup-profile/profile.zip so you can inspect trances in profile.json after startup completes.