From: Namhyung Kim <namhyung@kernel.org>
To: Dhaval Giani <dhaval.giani@gmail.com>
Cc: Arnaldo de Melo <acme@infradead.org>,
mingo@kernel.org, Peter Zijlstra <peterz@infradead.org>,
akshay kumar <iit.akshay@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] perf report: different reports when run on terminal as opposed to script
Date: Tue, 30 Oct 2012 16:42:44 +0900 [thread overview]
Message-ID: <871ugg76dn.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAPhKKr8KNi0kU4CcbPofZT7sghumeUTRyiuywOWrd24DiF4gFQ@mail.gmail.com> (Dhaval Giani's message of "Mon, 29 Oct 2012 12:45:53 -0400")
Hi Dhaval,
On Mon, 29 Oct 2012 12:45:53 -0400, Dhaval Giani wrote:
> On Mon, Oct 29, 2012 at 12:01 PM, Dhaval Giani <dhaval.giani@gmail.com> wrote:
>> Hi,
>>
>> As part of a class assignment I have to collect some performance
>> statistics. In order to do so I run
>>
>> perf record -g <the program I have to profile>
>>
>> And in another window, I start 200 threads of the load generator
>> (which is not recorded by perf)
>>
>> This generates me statistics that I expect to see, and I am happy. As
>> this is academia and a class assignment, I need to collect information
>> and analyze it across different setups. Which of course meant I script
>> this whole thing, which basically is
>>
>> for i in all possibilities
>> do
>> perf record -g <the program I have to profile> &
>> WAITPID=$!
>> for j in NR_THREADS
>> do
>> <start load generator> &
>> KILLPID=$!
>> done
>> wait $PID
You meant $WAITPID, right?
>> kill $KILLPID
Doesn't it kill the last load generator only?
>> mv perf.data results/perf.data.$i
>> done
>>
>> (This is basic pseudo script of what I am doing), which results me
>> having my profile being topped by _vscanf() and the function which I
>> was seeing dominating in the older report dropping down to something
>> like 5% (as opposed to 16-17%)
>>
>> Have I misunderstood how perf works? Something deeper? I am currently
>> on 3.6.3. I can update to the latest upstream and report back. Any
>> debug code is very welcome. I can also make my toy program and the
>> scripts available for you to try out.
>
> I just updated to 6b0cb4eef7bdaa27b8021ea81813fba330a2d94d and I still
> see this happen.
>
> Thanks!
> Dhaval
next prev parent reply other threads:[~2012-10-30 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 16:01 [BUG] perf report: different reports when run on terminal as opposed to script Dhaval Giani
2012-10-29 16:45 ` Dhaval Giani
2012-10-30 7:42 ` Namhyung Kim [this message]
2012-10-30 12:05 ` Dhaval Giani
2012-10-31 7:12 ` Namhyung Kim
2012-10-31 22:15 ` Dhaval Giani
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=871ugg76dn.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@infradead.org \
--cc=dhaval.giani@gmail.com \
--cc=iit.akshay@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.