mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: John Mudd <johnbmudd@gmail.com>
Cc: musl <musl@lists.openwall.com>
Subject: Re: musl perf, 20% slower than native build?
Date: Wed, 8 Apr 2015 18:58:54 +0300 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.11.1504081849280.25387@monopod.intra.ispras.ru> (raw)
In-Reply-To: <CAGDMk9F2kt-sK6s4nW4QV=ixqiFk=iGeivUK=WbgGbrUPAfW6w@mail.gmail.com>

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


  reply	other threads:[~2015-04-08 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 15:33 John Mudd
2015-04-08 15:58 ` Alexander Monakov [this message]
2015-04-08 16:05 ` Szabolcs Nagy
2015-04-08 19:10   ` John Mudd
2015-04-08 19:28     ` Daniel Cegiełka
2015-04-08 20:59       ` Paul Schutte
2015-04-09  6:50         ` Daniel Cegiełka
2015-04-09 17:28         ` Execinfo.h, backtrace is needed Jean-Marc Pigeon
2015-04-09 17:34           ` Rich Felker
2015-04-09 17:57             ` Alexander Monakov
2015-04-10 14:30               ` Jean-Marc Pigeon
2015-04-08 19:33     ` musl perf, 20% slower than native build? Alexander Monakov
2015-04-08 20:16       ` John Mudd
2015-04-08 20:24         ` John Mudd
2015-04-08 21:48           ` John Mudd

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=alpine.LNX.2.11.1504081849280.25387@monopod.intra.ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=johnbmudd@gmail.com \
    --cc=musl@lists.openwall.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).