OProfileUI
OProfileUI is a user interface to the stochastic system profiler. OProfile, providing application developers and system integrators with a graphical view of hotspots in their applications and systems.
OProfileUI is Free Software released under the GNU GPLv2. Development of OProfileUI was sponsored by Nokia.
Features
Client/server model allowing the resource intensive profile generation to be completed off-target. This allows the profiling of resource limited targets, for instance embedded devices, from the comfort of a desktop system.
Wide range of hardware support. By basing this interface on OProfile we can support all architectures supported by OProfile. However our primary design platform is with ARM and x86 targets and x86 host.
Support for detailed profiling, including call-graph generation.
No need for extra instrumentation. With OProfile applications need no extra build-time instrumentation to be profileable. The only requirement is that the binaries of interest have debugging symbols 1).
Intuitive visual interface. By using colour to indicate resource usage along it makes it easy for the developer to see the resource usage at a glance. Combined with clear visual modes it is easy to identify the busiest applications on the system, the busiest libraries and the busiest symbols and drill down within those to find more detailed information.
Screenshot
Download
The current release of OProfileUI is 0.2.0. You can use the link below to fetch the source tarball.
Pre-built packages are available for Debian and Ubuntu are available in the repository.
OProfileUI requires certain version of OProfile to be installed, these are available in the repository listed above and are fully described in the README file within the tarball.
Older releases can be found in the download directory.
Development
For Development code, use Subversion;
svn co http://svn.o-hand.com/repos/oprofileui/trunk oprofileui
You can also browse the repository.
Feedback
Please contact the author, Rob Bradford with feedback and contributions.
1) on ARM it is necessary to build with -fno-omit-frame-pointer for call graphing to work