jrfonseca/gprof2dot

Converts profiling output to a dot graph.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 20th, 2026
Created on March 13th, 2015
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 391
Total Stargazers: 3,455 (+0)
Total Subscribers: 75 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

gprof2dot is a Python script that converts profiling output into dot graph visualizations.

The tool solves the problem of making profiler output human-readable and actionable by transforming raw profiling data into visual call graphs. It reads output from a wide range of profilers including Linux perf, Valgrind's callgrind, Sysprof, Xperf, VTune, Very Sleepy, Python's built-in profilers, Java's HPROF, gprof, DTrace, and FlameGraph's stackcollapse format. The generated dot graphs can be rendered using Graphviz into various image formats. The tool includes features to prune nodes and edges below specified thresholds, apply heuristics for handling mutually recursive functions, and use color to highlight performance hotspots. It can also compare two structurally similar graphs to analyze differences in performance metrics.

Developers should choose this tool when they need to visualize profiling data across multiple profiling tools and platforms. It works anywhere Python and Graphviz are available, making it suitable for cross-platform development workflows. The tool is particularly valuable for teams using different profilers across different languages and systems, as it provides a unified visualization approach. For interactive graph exploration, the README recommends pairing it with xdot.py.

The project's development is in maintenance mode. The maintainer explicitly states that the tool currently fulfills their needs with little time available for maintenance, meaning requested features are unlikely to be implemented and issue reports or pull requests may be processed slowly.