From: Andrew.McDermott@windriver.com (McDermott, Andrew)
Subject: [lttng-dev] status of lttng top
Date: Mon, 22 Oct 2012 11:00:03 +0000 [thread overview]
Message-ID: <7F632A9222059A42AF70FCB7965774AA20854D6F@ALA-MBB.corp.ad.wrs.com> (raw)
In-Reply-To: <507389DE.4000204@efficios.com> (Julien Desfossez's message of "Mon, 8 Oct 2012 22:20:14 -0400")
Hi,
> LTTngTop is still work in progress and will remain that way for a long
> time, but the version in the PPA (or in the master branch in git) is
> perfectly usable for offline traces (traces recorded and replayed
> through LTTngTop).
>
> The "live" branch is more experimental and requires patches in both
> Babeltrace and Lttng-tools (all documented in the README-LIVE file), but
> it worked at the time of Plumbers, I didn't have much time since then to
> rebase the branches.
>
> I am waiting for the release of Lttng-tools 2.1 (currently in RC) before
> merging those patches. After these patches are integrated, LTTngTop will
> be able to work live without any modifications, so directly reading
> traces in memory shared with the tracer.
Thanks for this info.
Right now my interest is with the live streaming; we have a use case
where the live streaming is really the only practical solution.
Very roughly, would you expect the RC series to conclude this year, or
(early) next year?
> In the meantime we are working on replacing the "home made" state system
> in LTTngTop with a more generic one (which will be used also in LTTV),
> this will cleanup this part of the code and allow to store the state on
> disk. So in a near future we will be able to only read the state instead
> of the trace (once it has been generated), which will compress
> significantly the amount of data we need to keep in order to access the
> kind of statistics provided by LTTngTop.
>
> If you want to try LTTngTop, you can just install the package and follow
> the man page to record a trace with the right contexts, it should work
> as is.
>
> If you have any questions and/or feedback, please don't hesitate to ask.
>
> Thanks,
>
> Julien
>
>
> On 08/10/12 05:57 PM, McDermott, Andrew wrote:
>> I was wondering what the status of lttng top was. I'm happy to add the
>> daily Ubuntu PPA and try it that way, or equally building from source.
>> But, before I tread that route, are there any gotchas to be aware of.
>> Is it still considered work-in-progress, etc.
>>
>> Thanks.
>>
>>
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2012-10-22 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 21:57 McDermott, Andrew
2012-10-09 2:20 ` Julien Desfossez
2012-10-22 11:00 ` McDermott, Andrew [this message]
2012-10-22 18:10 ` Julien Desfossez
2012-10-23 13:11 ` McDermott, Andrew
2012-10-25 18:40 ` Julien Desfossez
2012-10-26 12:40 ` McDermott, Andrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7F632A9222059A42AF70FCB7965774AA20854D6F@ALA-MBB.corp.ad.wrs.com \
--to=andrew.mcdermott@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox