Announce: Sysprof 1.0 -- a sampling, systemwide Linux profiler
* What is it?
--------------------------
Sysprof is a sampling system-wide CPU profiler for Linux.
Sysprof uses a Linux kernel module to profile the entire system, not just an individual application.
Of course, sysprof handles threads and shared libraries, and applications do not have to be recompiled or instrumented. In fact they don't even have to be restarted.
Just insert the kernel module and start sysprof.
* Features:
----------------------
- Profiles all running processes, not just a single application
- Call graph support showing time spent in each branch of the call tree
- Has a simple graphical interface
- Profiles can be loaded and saved
- Easy to use: Just insert the kernel module and start sysprof
- Supports Fedora debuginfo packages
* Sysprof 1.0
--------------------------
This is the first release of sysprof with a 1.x version number. I am very excited about that.
New features since Sysprof 0.91:
- support for x86-64, thanks to Mike Frysinger
- better reporting of time spent in the kernel
Please report bugs as well as success or failure stories to
sandmann@daimi au dk
* Where can I get it?
--------------------------------------------
Home page:
http://www.daimi.au.dk/~sandmann/sysprof/
Source code:
http://www.daimi.au.dk/~sandmann/sysprof/sysprof-1.0.tar.gz
Sysprof requires
- Linux 2.6.11 or later, compiled with profiling support
- GTK+ 2.6
- libglade 2.5
It is known to work out the box on Fedora Core 4.
Søren
Quoted 1 line · Soeren Sandmann
Sysprof is a sampling system-wide CPU profiler for Linux.
I didn't really understand you last time, so I may as well ask again in
public: what is the point in you re-implementing OProfile?
regards,
john
Quoted 7 lines · Soeren Sandmann
* What is it?
--------------------------Sysprof is a sampling system-wide CPU profiler for Linux.
Sysprof uses a Linux kernel module to profile the entire system, not just an individual application.
How is this different from oprofile?
Looks like you did an exact, but less capable, reimplementation.
Signature · 2 lines
http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services
Quoted 3 lines · bert hubert
How is this different from oprofile?
Looks like you did an exact, but less capable, reimplementation.
The kernel module is indeed less capable by itself, but the userspace tools are a lot easier to use and show you significantly more details. Oprofile may have improved since then, but when I started sysprof:
- oprofile didn't work on anything but smp kernels
- oprofile could not produce callgraph information without not only recompiling my kernel, but also patching the kernel
- oprofile had a user interface that I simply didn't understand. As I remember it, I had to know about performance counters and how to translate those into binary masks
Contrast with sysprof, where you
- insert the module
- hit the start button
- do the thing you want to profile
- hit the profile button
and you get data presented in a way that is just a whole lot more useful than the flat text files generated by oprofile.
Søren
Quoted 11 lines · Soeren Sandmann
details. Oprofile may have improved since then, but when I started sysprof:
- oprofile didn't work on anything but smp kernels
- oprofile could not produce callgraph information without not only recompiling my kernel, but also patching the kernel
- oprofile had a user interface that I simply didn't understand. As I remember it, I had to know about performance counters and how to translate those into binary masks
This is what you said first time I asked you, none of which explain why you're continuing this duplication of effort, since *none* of the above are true any more (and the first /never/ was).
Quoted 2 lines
and you get data presented in a way that is just a whole lot more useful than the flat text files generated by oprofile.
Building a GUI around OProfile would have been welcome, but you've chosen to re-implement the entire stack...
regards,
john
Quoted 5 lines · John Levon
Quoted 2 lines
and you get data presented in a way that is just a whole lot more useful than the flat text files generated by oprofile.
Building a GUI around OProfile would have been welcome, but you've chosen to re-implement the entire stack...
The only thing I have reimplemented is a kernel module. If you remove all the #if 0'd lines in sysprof-module.c you are left with 296 lines of code. So it's hardly a reimplementation of the entire stack.
And in fact I don't care all that much about the kernel module. The things I really care about, the gui and the analysis code, do not really have an equivalent in oprofile, and those two things are the meat of the sysprof package:
[ssp@localhost sysprof]$ cat *.[ch] | wc -l
6706
My motive is not to duplicate oprofile - I basically don't care about the kernel level mechanism as long as it can produce stack traces that the GUI can interprete and analyse. In fact, one of the first times I wrote about sysprof publicly [1], I said:
It seems to me that since oprofile probably reports more and better data than my kernel module, we should try and get the graphical presentation from sysprof to present oprofile data.
and I still think so, but it's a fairly substantial amount of work to get rid of 296 lines of code.
Soren
[1] http://www.redhat.com/archives/fedora-desktop-list/2004-May/msg00041.html
Hi,
Quoted 11 lines
My motive is not to duplicate oprofile - I basically don't care about the kernel level mechanism as long as it can produce stack traces that the GUI can interprete and analyse. In fact, one of the first times I wrote about sysprof publicly [1], I said:
It seems to me that since oprofile probably reports more and better data than my kernel module, we should try and get the graphical presentation from sysprof to present oprofile data.
and I still think so, but it's a fairly substantial amount of work to get rid of 296 lines of code.
Looking at your kernel module it should be pretty easy to plug on top of oprofile callgraph data. All the hard work of programming hardware performance counters will then come for free. Cross platform support will also come for free.
Anton
Quoted 5 lines · John Levon
Quoted 2 lines
and you get data presented in a way that is just a whole lot more useful than the flat text files generated by oprofile.
Building a GUI around OProfile would have been welcome, but you've chosen to re-implement the entire stack...
Sysprof seems to profile userspace simultanous, while oprofile is
bounded to kernel calls.
Signature · 2 lines
Tomasz Torcz 72->| 80->| [email protected] 72->| 80->|
Quoted 5 lines · Tomasz Torcz
Quoted 2 lines
Building a GUI around OProfile would have been welcome, but you've chosen to re-implement the entire stack...
Sysprof seems to profile userspace simultanous, while oprofile is
bounded to kernel calls.
I don't know how you got this idea, but it's completely wrong.
john
Quoted 3 lines
- oprofile had a user interface that I simply didn't understand. As I remember it, I had to know about performance counters and how to translate those into binary masks
This all hasn't been true for a very long while.
Quoted 2 lines
Contrast with sysprof, where you
- insert the module
modprobe oprofile
Quoted 1 line
- hit the start button
opcontrol --start --vmlinux=/boot/vmlinux
Quoted 2 lines
- do the thing you want to profile
- hit the profile button
opcontrol --stop
opreport -l
Quoted 2 lines
and you get data presented in a way that is just a whole lot more useful than the flat text files generated by oprofile.
Not *that* may be very true, and your GUI indeed looks very very promising. Elsewhere you note regarding removing your sysprof.o code:
Quoted 2 lines
and I still think so, but it's a fairly substantial amount of work to get rid of 296 lines of code.
You'll find this work orders of magnitude easier than convincing people that we need yet another profiling system in the kernel.
So I urge you, keep the cool gui but adapt it to oprofile. I'm sure John will be more than willing to work with you to make sure oprofile supports/will support everything you need.
Ok?
Signature · 2 lines
http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services