parca-dev/parca

Continuous profiling for analysis of CPU and memory usage, down to the line number and throughout time. Saving infrastructure cost, improving performance,...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 13th, 2026
Created on November 27th, 2018
Open Issues & Pull Requests: 207 (+0)
GitHub issues: Enabled
Number of forks: 259
Total Stargazers: 4,973 (+0)
Total Subscribers: 39 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.5 hours
Mean response time: 114.0 days
90th percentile: 360.1 days
Tracked items: 33

Most active contributors

Sign in to see contributor activity.

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 668 days
Stale 30+ days: 24
Stale 90+ days: 20

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • area/ui (8)
  • bug (4)
  • area/debuginfo (1)
  • area/symbolization (1)
  • enhancement (1)
  • good first issue (1)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Parca is a continuous profiling system that collects and analyzes CPU and memory usage data down to the line number across infrastructure over time.

Parca addresses the problem of identifying performance bottlenecks and resource waste in production systems without requiring code instrumentation. It uses an eBPF-based profiler that automatically discovers targets across Kubernetes or systemd environments with minimal overhead, supporting multiple languages including C, C++, Rust, Go, and others. The system produces and ingests pprof-formatted profiles, enabling interoperability with existing observability tools. Profiling data is stored efficiently while retaining raw data, allowing users to slice and aggregate information across infrastructure dimensions and compare profiles across different labels such as deploys, versions, and regions.

Organizations with significant resource waste in their infrastructure should consider Parca, particularly those running containerized or systemd-managed workloads where zero-instrumentation profiling is valuable. The tool suits teams investigating performance optimization opportunities, understanding memory leaks, and troubleshooting incidents where CPU or I/O spikes cause unexpected behavior. The project's approach of collecting continuous profiling data enables statistical confidence in identifying hot paths and comparing performance across different dimensions.

The project maintains active development with regular updates to both the profiling agent and the core system. The codebase spans multiple languages, with TypeScript used for the UI and Go for the backend components, reflecting the tool's need to handle both frontend visualization and low-level infrastructure profiling. Documentation and installation guidance are actively maintained on the project's website, and the team actively solicits feedback through GitHub Discussions to inform development priorities.