[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.11.1504081849280.25387@monopod.intra.ispras.ru>
Date: Wed, 8 Apr 2015 18:58:54 +0300 (MSK)
From: Alexander Monakov <amonakov@...ras.ru>
To: John Mudd <johnbmudd@...il.com>
cc: musl <musl@...ts.openwall.com>
Subject: Re: musl perf, 20% slower than native build?
On Wed, 8 Apr 2015, John Mudd wrote:
> I've also never used "perf" before. Feel free to advise if this needs
> improvement.
Yes, can you please also provide perf record/report output? Plain 'perf stat'
is good for a very high-level overview, but insufficient to understand where
performance is lost. Running `perf record python ...` will create 'perf.data'
file in current directory. Use `perf report` to view it, or `perf report
--stdio` to retrieve pasteable output (top 25 or so lines should do).
Thanks for looking into it.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
