From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Faster!
Date: Sat, 16 Mar 2013 17:43:03 +0100 [thread overview]
Message-ID: <87obejs3c8.fsf@gnu.org> (raw)
In-Reply-To: <878v7aidqj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 30 Jan 2013 22:04:52 +0100")
The saga continues!
With today’s commit, the execution time of
guix build -e '(@ (gnu packages emacs) emacs)' -d
is down from 1.54s to 1.08s on my 2.6 GHz laptop. That’s 30%. :-)
The head of the profile is now like this:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,pr (package-derivation s emacs)
% cumulative self
time seconds seconds name
29.07 0.35 0.33 write
8.14 0.09 0.09 search-path
6.98 0.09 0.08 open-file
5.81 0.07 0.07 read
4.65 0.51 0.05 call-with-output-string
4.65 0.05 0.05 %after-gc-thunk
3.49 0.04 0.04 hash-ref
2.33 0.24 0.03 write-derivation
2.33 0.07 0.03 bytevector-quintet-fold-right
2.33 0.03 0.03 #<procedure 23dc1c0 (_ _ _ _)>
2.33 0.03 0.03 hash-set!
2.33 0.03 0.03 display
[...]
0.00 0.79 0.00 build-expression->derivation
[...]
---
Sample count: 86
Total time: 1.125903012 seconds (0.152722833 seconds in GC)
--8<---------------cut here---------------end--------------->8---
IOW, the main bottleneck is in Guile’s ‘write’ and port output (as
called from ‘build-expression->derivation’).
We also do a lot of GC. This could be improved by optimizing the RPCs
in store.scm to allocate less.
Ludo’.
prev parent reply other threads:[~2013-03-16 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:15 Faster! Ludovic Courtès
2013-01-30 20:47 ` Faster! Andreas Enge
2013-01-30 21:04 ` Faster! Ludovic Courtès
2013-01-30 21:17 ` Faster! Andreas Enge
2013-01-30 22:04 ` Faster! Ludovic Courtès
2013-01-30 22:09 ` Faster! Andreas Enge
2013-01-30 22:51 ` Faster! Ludovic Courtès
2013-01-31 22:22 ` Faster! Ludovic Courtès
2013-02-04 19:12 ` Faster! Nikita Karetnikov
2013-02-04 21:37 ` Faster! Ludovic Courtès
2013-03-16 16:43 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obejs3c8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).