linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Selva <selva.manuel@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Manuel Selva <manuel.selva@insa-lyon.fr>,
	linux-perf-users@vger.kernel.org
Subject: Re: Understanding perf mem -t load results
Date: Mon, 16 Dec 2013 10:13:06 +0100	[thread overview]
Message-ID: <CALbiyZzWsDCANnhMsd9bsdqyjYtFNeSNUiUgvs7hSwH-w4ZZWw@mail.gmail.com> (raw)
In-Reply-To: <20131215234548.GP21717@two.firstfloor.org>

Thanks again.

I guess that by "how you configure perf" you are speaking about
thred/cpu, kernel/user parameters ? For now I am monitoring one
application only on a given node only and I am trying to setup things
in order to get useful results independently of the overhead. I'll
investigate overhead in a second time.

I can't use perf stat because I need to relate perf events with my
application's code.

Manu

2013/12/16 Andi Kleen <andi@firstfloor.org>:
> On Sun, Dec 15, 2013 at 11:03:13PM +0100, Manuel Selva wrote:
>> Thanks for the answer Andi.
>>
>> Is there any way (I couldn't find in the Intel documentation) to
>> have an approximation of the "maximum" acceptable frequency ?
>
> It depends on how much overhead is acceptable and how you configure
> perf (which affects the cost of the handler) and what the executed
> code does. You could tune it to minimize throttles.
>
> I would start with something like 20003
>
> If you only want the relative ratios of course using perf stat would
> be better.
>
> -Andi
>
> --
> ak@linux.intel.com -- Speaking for myself only.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-12-16  9:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 14:06 Understanding perf mem -t load results Manuel Selva
2013-12-15 18:27 ` Manuel Selva
2013-12-15 21:18 ` Andi Kleen
2013-12-15 22:03   ` Manuel Selva
2013-12-15 23:45     ` Andi Kleen
2013-12-16  9:13       ` Manuel Selva [this message]
2013-12-20  9:38         ` Manuel Selva
2013-12-24  2:18           ` Andi Kleen
2013-12-24  7:10             ` Manuel Selva
2013-12-24  7:28               ` Andi Kleen
2013-12-24  7:42                 ` Manuel Selva
2013-12-24 21:27                   ` Andi Kleen
2013-12-25 10:25                     ` Manuel Selva
2014-01-07 15:06                       ` Manuel Selva
2014-01-07 21:27                         ` Andi Kleen
2014-01-08  8:53                           ` Manuel Selva
2014-01-08  9:50                             ` Manuel Selva
2014-01-08 19:44                             ` Andi Kleen

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=CALbiyZzWsDCANnhMsd9bsdqyjYtFNeSNUiUgvs7hSwH-w4ZZWw@mail.gmail.com \
    --to=selva.manuel@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=manuel.selva@insa-lyon.fr \
    /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).