From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <138575260907091140x5ba35a61l5fddb885302b861d@mail.gmail.com> References: <138575260907091140x5ba35a61l5fddb885302b861d@mail.gmail.com> Date: Thu, 9 Jul 2009 14:26:52 -0500 Message-ID: From: Jason Catena To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] data analysis on plan9 Topicbox-Message-UUID: 195e76a2-ead5-11e9-9d60-3106f5b1d025 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