From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: Guile Devel <guile-devel@gnu.org>
Cc: lilypond-devel <lilypond-devel@gnu.org>
Subject: useful statprof data?
Date: Sat, 18 Jul 2020 22:10:24 +0200 [thread overview]
Message-ID: <CAOw_e7babrTzD1qo40j9jO+e2DY7TrUQ_5_4MW+bsGWPHzOJzQ@mail.gmail.com> (raw)
We finally have a version of LilyPond that can work with byte compiled
files on GUILE 3. I had high hopes for this, given the ebullient
promises of JIT in the release announcement. The results are
disappointing. GUILE 3.0 is 3% faster than GUILE 2.2; both are about
30% slower than GUILE 1.8
I wanted to look more into the cause of this, and tried to run statprof.
This prints a ton of
;;; (what! #<stack 7f60fbf7fc20>)
lines. Then, the results look like
97.2% #x221bfb4
27.6% #x2215134
27.4% #x221836c
15.6% #x2215138
15.6% #x220ae70
15.6% profile-signal-handler at statprof.scm:251:4
15.6% #x2212b88
6.7% #x2218430
6.7% #x220ae70
6.7% profile-signal-handler at statprof.scm:251:4
6.7% #x2212b88
Is there a way to get insight into what these hex addresses (?) mean?
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
reply other threads:[~2020-07-18 20:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOw_e7babrTzD1qo40j9jO+e2DY7TrUQ_5_4MW+bsGWPHzOJzQ@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=lilypond-devel@gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).