From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/7357
Path: news.gmane.org!not-for-mail
From: Alexander Monakov <amonakov@ispras.ru>
Newsgroups: gmane.linux.lib.musl.general
Subject: Re: musl perf, 20% slower than native build?
Date: Wed, 8 Apr 2015 18:58:54 +0300 (MSK)
Message-ID: <alpine.LNX.2.11.1504081849280.25387@monopod.intra.ispras.ru>
References: <CAGDMk9F2kt-sK6s4nW4QV=ixqiFk=iGeivUK=WbgGbrUPAfW6w@mail.gmail.com>
Reply-To: musl@lists.openwall.com
NNTP-Posting-Host: plane.gmane.org
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Trace: ger.gmane.org 1428508761 17525 80.91.229.3 (8 Apr 2015 15:59:21 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Wed, 8 Apr 2015 15:59:21 +0000 (UTC)
Cc: musl <musl@lists.openwall.com>
To: John Mudd <johnbmudd@gmail.com>
Original-X-From: musl-return-7370-gllmg-musl=m.gmane.org@lists.openwall.com Wed Apr 08 17:59:08 2015
Return-path: <musl-return-7370-gllmg-musl=m.gmane.org@lists.openwall.com>
Envelope-to: gllmg-musl@m.gmane.org
Original-Received: from mother.openwall.net ([195.42.179.200])
	by plane.gmane.org with smtp (Exim 4.69)
	(envelope-from <musl-return-7370-gllmg-musl=m.gmane.org@lists.openwall.com>)
	id 1YfsNf-0004l4-So
	for gllmg-musl@m.gmane.org; Wed, 08 Apr 2015 17:59:08 +0200
Original-Received: (qmail 26054 invoked by uid 550); 8 Apr 2015 15:59:06 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
Original-Received: (qmail 26036 invoked from network); 8 Apr 2015 15:59:06 -0000
In-Reply-To: <CAGDMk9F2kt-sK6s4nW4QV=ixqiFk=iGeivUK=WbgGbrUPAfW6w@mail.gmail.com>
User-Agent: Alpine 2.11 (LNX 23 2013-08-11)
Xref: news.gmane.org gmane.linux.lib.musl.general:7357
Archived-At: <http://permalink.gmane.org/gmane.linux.lib.musl.general/7357>

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