Messages in this thread | | | Subject | Re: Announce: Sysprof 1.1.2 CPU profiler for Linux | From | Soeren Sandmann <> | Date | 13 Oct 2009 22:13:54 +0200 |
| |
Ingo Molnar <mingo@elte.hu> writes:
> * Christoph Hellwig <hch@infradead.org> wrote: > > > On Sat, Sep 26, 2009 at 05:46:23PM +0200, Soeren Sandmann wrote: > > > Sysprof 1.1.2 is now available. This is a development release leading > > > up to a stable 1.2.0 release. > > > > > > Sysprof is a sampling system-wide CPU profiler for Linux. This > > > version is based on the perf counter interface in 2.6.31 kernels and > > > will not work with earlier kernels. > > > > Btw, what is the plan for the sysprof ftrace plugin? In general we > > move away from ftrace plugins towards trace events and perf, and if I > > remember correctly ftrace file format changes caused enough pain for > > sysprof that it kept shipping it's old hacky kernel module.
Missed this mail somehow. The main issue with the ftrace plugin was performance. Often, 20% of the time, as reported by sysprof was spent in the ftrace read() interface. I think some of that came from the locking code compiled with debug information, but even without that, there was significant overhead.
The perf counter interface works very well and will eventually allow a number of new features to be added.
> > Is it time to deprectate the sysprof ftrace plugin? > > Yes - but it's minimal maintenance overhead so we want to keep it for > kernel release or two, to sunset it properly.
Makes sense to me.
Thanks, Soren
| |