All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Mike Galbraith <efault@gmx.de>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [patch] perf_counter tools: remove expensive old debug code from perf top
Date: Tue, 13 Oct 2009 11:43:12 -0300	[thread overview]
Message-ID: <20091013144312.GE21809@ghostprotocols.net> (raw)
In-Reply-To: <1255444919.7042.2.camel@marge.simson.net>

Em Tue, Oct 13, 2009 at 04:41:59PM +0200, Mike Galbraith escreveu:
> On Tue, 2009-10-13 at 15:37 +0200, Ingo Molnar wrote:
> > * Mike Galbraith <efault@gmx.de> wrote:
> > 
> > > perf_counter tools: remove expensive old debug code from perf top
> > > 
> > > Calling gettimeofday() at high frequency is painful for handicapped 
> > > boxen. The spot calling gettimeofday() is old unneeded debug code, so 
> > > remove it.
> > 
> > Thanks!
> > 
> > We still seem to have a performance problem. Just running perf top on a 
> > 16-way box:
> > 
> >  Performance counter stats for 'perf top -e cycles -c 3000000':
> > 
> >      585.694831  task-clock-msecs         #      0.113 CPUs 
> >           35163  context-switches         #      0.060 M/sec
> >              17  CPU-migrations           #      0.000 M/sec
> >           20355  page-faults              #      0.035 M/sec
> >      1476952962  cycles                   #   2521.711 M/sec
> >       730770658  instructions             #      0.495 IPC  
> >        11489471  cache-references         #     19.617 M/sec
> >         2055001  cache-misses             #      3.509 M/sec
> > 
> >     5.169518576  seconds time elapsed
> > 
> > that's 11% of CPU time used on a single CPU - just displaying a measly 
> > 16K irqs/sec. Something's not quite right here.
> 
> I'll try to figure out why after I do some more wakeup preempt testing.
> 
> btw, something broke top annotation (again).  Module symbols still
> annotate, but vmlinux symbols went south.

I'll check this one, and I'm profiling perf top as well.

- Arnaldo

      reply	other threads:[~2009-10-13 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 12:57 [patch] perf_counter tools: remove expensive old debug code from perf top Mike Galbraith
2009-10-13 13:34 ` [tip:perf/core] perf tools: Remove " tip-bot for Mike Galbraith
2009-10-13 13:37 ` [patch] perf_counter tools: remove " Ingo Molnar
2009-10-13 14:41   ` Mike Galbraith
2009-10-13 14:43     ` Arnaldo Carvalho de Melo [this message]

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=20091013144312.GE21809@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.