public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Eric B Munson <ebmunson@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] perf: Fix performance issue with perf report
Date: Tue, 4 May 2010 21:19:15 +1000	[thread overview]
Message-ID: <20100504111915.GB14636@kryten> (raw)


On a large machine we spend a lot of time in perf_header__find_attr when
running perf report. 

If we are parsing a file without PERF_SAMPLE_ID then for each sample we call
perf_header__find_attr and loop through all counter IDs, never finding a match.
As the machine gets larger there are more per cpu counters and we spend an
awful lot of time in there.

The patch below initialises each sample id to -1ULL and checks for this in
perf_header__find_attr. We may need to do something more intelligent eventually
(eg a hash lookup from counter id to attr) but this at least fixes the most
common usage of perf report.

Signed-off-by: Anton Blanchard <anton@samba.org>
--

Index: linux.trees.git/tools/perf/util/event.c
===================================================================
--- linux.trees.git.orig/tools/perf/util/event.c	2010-05-03 20:20:54.000000000 +1000
+++ linux.trees.git/tools/perf/util/event.c	2010-05-04 21:15:20.000000000 +1000
@@ -713,6 +713,7 @@ int event__parse_sample(event_t *event, 
 		array++;
 	}
 
+	data->id = -1ULL;
 	if (type & PERF_SAMPLE_ID) {
 		data->id = *array;
 		array++;
Index: linux.trees.git/tools/perf/util/header.c
===================================================================
--- linux.trees.git.orig/tools/perf/util/header.c	2010-05-03 20:20:54.000000000 +1000
+++ linux.trees.git/tools/perf/util/header.c	2010-05-04 21:15:20.000000000 +1000
@@ -923,6 +923,14 @@ perf_header__find_attr(u64 id, struct pe
 {
 	int i;
 
+	/*
+	 * We set id to -1 if the data file doesn't contain sample
+	 * ids. Check for this and avoid walking through the entire
+	 * list of ids which may be large.
+	 */
+	if (id == -1ULL)
+		return NULL;
+
 	for (i = 0; i < header->attrs; i++) {
 		struct perf_header_attr *attr = header->attr[i];
 		int j;

             reply	other threads:[~2010-05-04 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 11:19 Anton Blanchard [this message]
2010-05-04 11:56 ` [PATCH] perf: Fix performance issue with perf report Eric B Munson
2010-05-04 17:04 ` [tip:perf/core] " tip-bot for Anton Blanchard

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=20100504111915.GB14636@kryten \
    --to=anton@samba.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=ebmunson@us.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox