Profiling Viewer Alternatives

Profiling Viewer

Profiling Viewer opens and visualizes callgrind files. You can use Treemap, Callgraph, flat or hierarchic lists to identify functions where your application spends more time than expected.

You can generate the required callgrind profiling data with various external tools available for many platforms and programming languages.
For example, you can open callgrind files generated by the Xdebug extension for PHP, Valgrind, Ruby ruby-prof, Python cProfile with pyprof2calltree, gperftools-pprof, Golang with pprof, Node.js with Valgrind or nodegrind and many other profiling tools with callgrind file output.

Features
- Function costs visualized as Treemap, Callgraph and Lists
- System functions can be hidden based on customizable presets
- Drill down through double-click, mouseover for details
- Source file Viewer annotated with costs and color marks
- Configurable source locations
- Displays costs as raw data or as percent
- Handles multiple costs and position types
- Shows cycles and recursions
- Sort data by costs, function name or filename
- Navigation history
- Parses compressed callgrind files
- Small memory footprint (for example, approximately 280 MB memory used to open and display a 4.6 GB callgrind file generated by xdebug)

The callgraph view is:
- Zoomable and supports trackpad gestures like zoom in, zoom out, smart zoom
- Represents call costs by the thickness of connections
- Its complexity can be reduced by hiding functions with cost below a customizable preset

Profiling Viewer uses graphviz to layout and render callgraphs. Graphviz is licensed under the Eclipse Public License v1.0. You can download graphviz at http://www.graphviz.org