From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: compile-file execution time driven by `reap-pipes'
Date: Mon, 6 Apr 2020 19:50:13 -0700 [thread overview]
Message-ID: <65448df1-5fd7-c0c3-852c-432c093915b2@gmail.com> (raw)
I'm wanted to trace down why some of my "compile-file" w/ no optimization
was tasking time. I was able to turn compile-file under statprof for one
of the moderate sized .scm files, which has about 45,000 lines of code.
It was interesting that the major execution time consumer was reap-pipes.
I'm curious where that fits in. Does anyone know how compile-file could
be banging on reap-pipes so much? Below is the top output from statprof.
The results are for a run using guile 3.0.2 on Ubunu 18.04/x86_64.
% cumulative self calls
time seconds seconds procedure
12.67 190.96 154.99 ice-9/popen.scm:145:0:reap-pipes
12.30 363.41 150.49 language/cps/intset.scm:270:2:adjoin
11.23 270.27 137.34 anon #x55befcb4c430
10.89 186.95 133.18 language/cps/slot-allocation.scm:843:19
10.58 129.40 129.40 language/cps/intmap.scm:396:0:intmap-ref
5.31 1279.35 64.90 language/cps/intmap.scm:247:2:adjoin
3.81 228.54 46.66 language/cps/intset.scm:269:0:intset-add
3.48 4695.90 42.60 language/cps/intset.scm:470:5:visit-branch
3.28 40.14 40.14 language/cps/intset.scm:349:0:intset-ref
2.98 567.14 36.46 language/cps/intmap.scm:246:0:intmap-add
next reply other threads:[~2020-04-07 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 2:50 Matt Wette [this message]
2020-05-17 21:39 ` compile-file execution time driven by `reap-pipes' Ludovic Courtès
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=65448df1-5fd7-c0c3-852c-432c093915b2@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-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).