From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Guile Devel <guile-devel@gnu.org>
Subject: Re: The size of ‘.go’ files
Date: Sat, 06 Jun 2020 10:20:44 +0200 [thread overview]
Message-ID: <87r1usli5f.fsf@gnu.org> (raw)
In-Reply-To: 875zc5z18d.fsf@gnu.org
Hey Ludo,
> $ guix size $(readlink -f /run/current-system) | head -5
> store item total self
> /gnu/store/4d0p06xgaw8lqa9db0d6728kkba8bizj-qemu-5.0.0 1651.6 745.2 18.8%
> /gnu/store/abiva5ivq99x30r2s9pa3jj0pv9g16sv-guix-1.1.0-4.bdc801e 468.0 268.8 6.8%
> /gnu/store/111zp1qyind7hsnvrm5830jhankmx4ls-linux-libre-5.4.43 243.6 243.6 6.2%
> /gnu/store/skxkrhgn9z0fg9hmnbcyfdgzs5w4ryrr-llvm-9.0.1 199.9 128.5 3.2%
When building a bare-bones Guix System disk-image, "Guix", "Guile" and
"Guile-static" represent 331M of .go files, see:
--8<---------------cut here---------------start------------->8---
find /gnu/store/fvvpmrgnvr9jqxfn5m956xblisa8vzr4-guix-1.1.0-4.bdc801e
/gnu/store/ljcrz0d86r20phszvj6s1mdyjchz79ja-guile-static-stripped-3.0.2
/gnu/store/18hp7flyb3yid3yp49i6qcdq0sbi5l1n-guile-3.0.2-name "*.go"
-print0| du --files0-from=- -hc |tail -n1
--8<---------------cut here---------------end--------------->8---
If we compare it to the 943M of the "reduced" image I'm working on, it
makes around 1/3 of the final image.
> With 3.0.3-to-be and -O1, python-xyz.go weighs in at 3.4 MiB instead of
> 5.9 MiB! Here’s the section size distribution:
Wooh, interesting!
Having a lighter disk-image isn't very important on desktop, but for the
embedded devices with small eMMC, any improvement would be really
welcome :)
Thanks,
Mathieu
next prev parent reply other threads:[~2020-06-06 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:50 The size of ‘.go’ files Ludovic Courtès
2020-06-06 8:20 ` Mathieu Othacehe [this message]
2020-06-06 19:21 ` Katherine Cox-Buday
2020-06-07 9:07 ` Pierre Neidhardt
2020-06-08 8:07 ` Andy Wingo
2020-06-09 16:09 ` Ludovic Courtès
2020-06-24 12:11 ` Andy Wingo
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=87r1usli5f.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).