grafana/pyroscope

Continuous Profiling Platform. Debug performance issues down to a single line of code

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 31st, 2020
Open Issues & Pull Requests: 405 (+0)
GitHub issues: Enabled
Number of forks: 799
Total Stargazers: 11,650 (+1)
Total Subscribers: 92 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Pyroscope is a continuous profiling platform that helps developers identify and resolve performance bottlenecks by collecting and analyzing CPU, memory, and I/O profiling data from running applications down to individual lines of code.

The platform addresses the challenge of understanding application performance in production by collecting profiling data continuously rather than on-demand. Pyroscope ingests profiles through multiple paths: native SDKs that push data, Grafana Alloy for pull or push collection, or OpenTelemetry-compatible sources including eBPF profilers. The v2 architecture simplifies operations by writing profiles directly to object storage, eliminating the need for in-memory ingesters and local disk storage. Background compaction workers merge small profile segments into larger blocks, while queries fan out across object storage to construct flame graphs for analysis through the Grafana Profiles Drilldown interface.

Teams should adopt Pyroscope when they need both proactive performance optimization—reducing resource consumption and preventing latency issues—and reactive incident response with line-level debugging capability. The tool suits organizations running applications in Go, Python, Ruby, and other supported languages where understanding resource usage patterns across services is critical. The v2 architecture makes it particularly attractive for teams operating at scale, as it reduces infrastructure complexity and resource overhead compared to systems requiring dedicated ingester nodes and local storage.

The project maintains active development with regular updates to its core architecture and tooling. The codebase is written primarily in Go and integrates deeply with the Grafana ecosystem, including native support for Grafana's visualization and querying interfaces. Migration paths exist for teams running v1 deployments, with documentation and guides provided to enable upgrades without data loss.