Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: benjamin.poirier@polymtl.ca (Benjamin Poirier)
Subject: [ltt-dev] LTTng net_extended_trace - example data
Date: Wed, 03 Feb 2010 14:36:48 -0500	[thread overview]
Message-ID: <4B69D050.3000701@polymtl.ca> (raw)
In-Reply-To: <OF0CAC194D.47B643A7-ONC12576BF.005F47B5-C12576BF.00603075@inf.mit.bme.hu>

Hello Gergely,

You can find a set of traces, results57, which work with the newest lttv at
http://lttng.org/~ben/results57.tar.bz2

These work with lttv 0.12.29
http://lttng.org/files/packages/lttv-0.12.29-02022010.tar.gz
and with the current git head.

Compile and install lttv from the tar archive, then run:
lttv-gui --sync --sync-stats -t results57/node1 -t results57/node2
If you are confortable building from git, you can compile and then run:
./runlttv -a"--sync --sync-stats" results57/node*

These traces showcase two programs: "broadcaster" which is a traffic
generator and an ssh session, which is more interesting.

Have a look around time 3092s, pid 1896 on node2 is the ssh client and
pid 1927 on node1 is the sshd server. The two are running on different
machines but the traces align accurately. In this case, the average
accuracy is +/- 28us. You can compare this without synchronization:
rerun lttv without the --sync options. The client and server are miles
appart.

If you'd like to try out advanced synchronization options, have a look
at lttv/lttv/sync/README. If you encounter problems or have further
questions, you are welcome to contact me or the ltt-dev mailing list again.

-Ben

paljak at mit.bme.hu wrote:
> Dear Benjamin,
>
> I am writing about your net_extended_trace extension to LTTng, I am
> evaluating it for a project. I looked up your e-mail announcing it on
> the lttng-dev mailing list, and I wanted to download the sample data
> from here: http://hal.drap.polymtl.ca/results55.tar.bz2 , but it is no
> longer available.
>
> Could you send it by e-mail or make it available somewhere online? I'd
> like to check out a sample before digging too deep into LTTng if it
> fits the needs of the project.
>
> Thank you very much in advance!
>
> Yours sincerely,
> Gergely
>
> -- 
> Gergely Paljak
> PhD Student
> Budapest University of Technology and Economics 




           reply	other threads:[~2010-02-03 19:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <OF0CAC194D.47B643A7-ONC12576BF.005F47B5-C12576BF.00603075@inf.mit.bme.hu>]

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=4B69D050.3000701@polymtl.ca \
    --to=benjamin.poirier@polymtl.ca \
    /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