Profiler

gProfiler is a Linux profiling tool that combines multiple sampling profilers to show what your CPU spends time on, with stack traces across native, Golang,…

  • Monitoring & Logging
  • Tools & Utilities
gProfiler is a Linux profiling tool that combines multiple sampling profilers to show what your CPU spends time on, with stack traces across native, Golang, Java, and Python runtimes plus kernel routines, so you can diagnose performance issues across your whole cluster.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
91last commit 31 days ago
Popular
58840 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
95no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
840
Open issues
129
Last commit
2026-10-21
Latest release
1.57.1
License
Apache-2.0
Activity
rising

Checked 15 days ago - source: GitHub (intel/gprofiler)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install and load the module first Run Install-Module Profiler, then Import-Module Profiler and check with Get-Module Profiler. This matters because the profiling commands won't work until the module is installed and loaded in your PowerShell session. source
  • Wrap your script in Trace-Script Use $trace = Trace-Script -ScriptBlock { & './YourScript.ps1' } instead of running the script directly. This captures the data the module needs so you can later see which lines are slow. source
  • Look at the slowest lines to fix it Check $trace.Top50SelfDuration to find lines doing the most work, then use Get-CallStack -Hit on one hit to see how you got there. This stops you from guessing which part of the script needs optimization. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I fix profiling 404 errors on a self-hosted instance?

Upgrade to 25.6.0, which adds the profile-chunks container, and then send new profiling data.

How does the profiler reduce storage use for profile data?

It uses efficient data storage and compression while preserving resolution.

How do I control a .NET profiling session from application code?

Reference the Profiler.SelfApi NuGet package in the project. The self-profiling API controls the session through the dotTrace command-line tool.

What should a self-hosted PHP profiler find in production?

It should detect bottlenecks in PHP workloads.

Answers sourced from github.com, www.jetbrains.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads