This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Any post performance analyzer tool suitable for LKET ?


We plan to add the visual analyzer to the SystemTap GUI. I would love to
get the hold of your trace data (binary or ascii) to start with.

Thanks, Hien.

Li Guanglei wrote:
> Hi folks,
>
>   LKET is actually an extension to SystemTap's tapsets library.
> It defines a set of event hooks that probe pre-defined places inside
> the Linux Kernel and will dump the traced data into disk.
>
>   Although LKET has a simple post-processing tool named lket-b2a which
> will convert the traced data from binary format into ascii format, I
> don't think it will be of much use for data analysis. My testing shows
> that LKET will generate several GB trace data for some combinations of
> event hooks and benchmarks. So without a good post-processing tool,
> it's hard to dig out useful information from such a large volume trace
> data.
>
>   I know Vara's team is doing SystemTap GUI, but it seems to me its
> main focus is to be a front-end of SystemTap while not a post
> performance analyzer.
>
>   So is there anyone/team working or planning to work on a
> visualization post-processing tool, i.e a performance analyzer that
> will be possible to support performance analysis of LKET's trace data?
>
>   I think by having a good performance analyzer tool, more people will
> find LKET/SystemTap more attractive and are willing to use
> LKET/SystemTap, then we can get more feedbacks and make it better.
>
>   For more details of LKET, you can refer to:
> http://sourceware.org/systemtap/man5/lket.5.html
>   Note that the event hooks and data format is not the final version.
>
>   Thanks for your attention.
>
> - Guanglei
>
>   


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]