From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>, acme@ghostprotocols.net
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Mike Galbraith <efault@gmx.de>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf record: mmap output file - RFC
Date: Thu, 26 Sep 2013 17:17:47 -0600 [thread overview]
Message-ID: <5244C09B.7040500@gmail.com> (raw)
In-Reply-To: <20130926175105.GB9121@krava.brq.redhat.com>
On 9/26/13 11:51 AM, Jiri Olsa wrote:
> but it's still faster, since we finally get perf a chance to sleep ;-)
>
> new time:
> real 0m30.392s
> user 0m0.041s
> sys 0m0.389s
>
> old time:
> real 0m32.235s
> user 0m3.080s
> sys 0m14.444s
>
Another data point on the performance improvement of perf itself. Using
openssl speed as a workload and perf-stat to collect information about
the perf-record process only:
perf stat -i -- perf record -g -o /tmp/perf.data openssl speed aes
With write():
158.606380 task-clock
72 context-switches
34 cpu-migrations
5,400 page-faults
336,054,007 cycles
137,804,036 stalled-cycles-frontend
74,505,914 stalled-cycles-backend
474,401,639 instructions
91,246,072 branches
1,968,289 branch-misses
With mmap():
50.314270 task-clock
61 context-switches
7 cpu-migrations
3,958 page-faults
93,585,618 cycles
64,878,225 stalled-cycles-frontend
41,680,427 stalled-cycles-backend
81,552,219 instructions
15,301,389 branches
387,230 branch-misses
So time, CPU cycles, instructions all drop by more than a factor of 3.
David
next prev parent reply other threads:[~2013-09-26 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 2:05 [PATCH] perf record: mmap output file - RFC David Ahern
2013-09-26 17:51 ` Jiri Olsa
2013-09-26 18:12 ` David Ahern
2013-09-26 18:23 ` Jiri Olsa
2013-09-26 23:17 ` David Ahern [this message]
2013-09-27 6:29 ` Ingo Molnar
2013-09-27 2:24 ` Namhyung Kim
2013-10-09 13:33 ` Jiri Olsa
2013-10-09 13:46 ` David Ahern
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=5244C09B.7040500@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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.