mailing list of musl libc
 help / color / mirror / code / Atom feed
From: John Mudd <johnbmudd@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: musl <musl@lists.openwall.com>, John Mudd <johnbmudd@gmail.com>
Subject: Re: musl perf, 20% slower than native build?
Date: Wed, 8 Apr 2015 17:48:37 -0400	[thread overview]
Message-ID: <CAGDMk9HP3T7mJUiLoRJROJgjkJAemNMk4QRwnu6faMCSCVgrCA@mail.gmail.com> (raw)
In-Reply-To: <CAGDMk9EZ6Cr2JaeQ_ZVHUr5-MQ3qb4e+676qU4i2jYaVmU9h8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]

Reran benchmark using -O3 musl library and now musl and native have
basically the same run times.

native:
     2.08%   python  libc-2.19.so         [.] __memcpy_ssse3
     0.81%   python  libc-2.19.so         [.] __x86.get_pc_thunk.bx
     0.56%   python  libc-2.19.so         [.] __memset_sse2
     0.53%   python  libc-2.19.so         [.] _int_malloc
     0.45%   python  libc-2.19.so         [.] _int_free
     0.40%   python  libc-2.19.so         [.] malloc
     0.22%   python  libc-2.19.so         [.] realloc
     0.21%   python  libc-2.19.so         [.] __ctype_b_loc
     0.12%   python  libc-2.19.so         [.] __x86.get_pc_thunk.cx
     0.12%   python  libc-2.19.so         [.] free
     0.01%   python  libc-2.19.so         [.] __strlen_sse2_bsf
     0.01%   python  libc-2.19.so         [.] malloc_consolidate
     0.01%   python  libc-2.19.so         [.] __memcpy_ia32
     0.00%   python  libc-2.19.so         [.] _IO_getc
     0.00%   python  libc-2.19.so         [.] mremap_chunk
     0.00%   python  libc-2.19.so         [.] _int_realloc
     0.00%   python  libc-2.19.so         [.] __strcmp_ssse3


musl:
     5.37%   python  libc.so              [.] memcpy
     1.96%   python  libc.so              [.] malloc
     1.93%   python  libc.so              [.] free
     0.60%   python  libc.so              [.] memset
     0.20%   python  libc.so              [.] __x86.get_pc_thunk.bx
     0.12%   python  libc.so              [.] realloc
     0.03%   python  libc.so              [.] alloc_fwd
     0.02%   python  libc.so              [.] alloc_rev
     0.01%   python  libc.so              [.] find_sym
     0.01%   python  libc.so              [.] strcmp
     0.00%   python  libc.so              [.] memcmp
     0.00%   python  libc.so              [.] __vm_lock
     0.00%   python  libc.so              [.] __strerror_l
     0.00%   python  libc.so              [.] __cp_end
     0.00%   python  libc.so              [.] .L350
     0.00%   python  libc.so              [.] strlen
     0.00%   python  libc.so              [.] memchr
     0.00%   python  libc.so              [.] pthread_rwlock_trywrlock




On Wed, Apr 8, 2015 at 4:24 PM, John Mudd <johnbmudd@gmail.com> wrote:

> Ignore my previous email. The symbols are there. I'll rebuild again and
> check the speed...
>
> On Wed, Apr 8, 2015 at 4:16 PM, John Mudd <johnbmudd@gmail.com> wrote:
>
>> I don't see any of those "a_*" names in the output of 'nm' or 'readelf
>> -a' on musl-1.1.8/lib/libc.so.
>>
>>>
>>>
>>
>

[-- Attachment #2: Type: text/html, Size: 4685 bytes --]

      reply	other threads:[~2015-04-08 21:48 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
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 [this message]

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=CAGDMk9HP3T7mJUiLoRJROJgjkJAemNMk4QRwnu6faMCSCVgrCA@mail.gmail.com \
    --to=johnbmudd@gmail.com \
    --cc=amonakov@ispras.ru \
    --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).