9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] data analysis on plan9
Date: Thu,  9 Jul 2009 14:26:52 -0500	[thread overview]
Message-ID: <d50d7d460907091226i2dbbf3d7k90716f0fc9d3e212@mail.gmail.com> (raw)
In-Reply-To: <138575260907091140x5ba35a61l5fddb885302b861d@mail.gmail.com>

I'd also be interested in knowing whether gnuplot or an equivalent is
yet ported to Plan 9.  Ron Minnich et al. seem to prefer gnuplot, and
reported that they generated data for it and used it in a paper, but
weren't specific whether the gnuplot ran on the same plan9 box or
another *nix.

>From http://doc.cat-v.org/plan_9/IWP9/2008/trace.pdf pp. 19-21:

"4.1 Visualizing trace device output

Once we had the data, we needed a way to analyse the information. After
working with the data for a while, we realized that the output as
shown in Figure
1 would be very useful. No graphiing [sic] tool available to us in
Plan 9 or Linux
was able to create that output. In the end, we determined that gnuplot was the
most appropriate tool, but even then the data required significant processing to
get it into the proper form.

We wrote a suite of scripts usng rc, the plan 9 shell; acid, the Plan
9 debugger;
awk, and sed to generate data appropriate for plotting with gnuplot.
The createplot
script has the ability to filter out functions which ran for less than
a specified number of clock cycles, which is useful for reducing the amount of
noise in a plot. To generate a plot from the data collected earlier, discarding
functions which completed in less than 4000 cycles, we just ran:

    plots/createplot /amd64/9k8pf 4000 ./trace > plotme

and fed the input into gnuplot."

Jason Catena



  parent reply	other threads:[~2009-07-09 19:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 18:40 hugo rivera
2009-07-09 18:56 ` Federico G. Benavento
2009-07-10  1:40   ` Roman V Shaposhnik
2009-07-10  1:49     ` John Floren
2009-07-10  1:54       ` erik quanstrom
2009-07-10  6:56     ` Steve Simon
2009-07-09 19:26 ` Jason Catena [this message]
2009-07-09 19:34   ` ron minnich
2009-07-09 19:56     ` J. R. Mauro
2009-07-09 19:54 ` J. R. Mauro

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=d50d7d460907091226i2dbbf3d7k90716f0fc9d3e212@mail.gmail.com \
    --to=jason.catena@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).