From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Tiny Guix (and containers)
Date: Thu, 26 Oct 2017 12:42:59 +0200 [thread overview]
Message-ID: <20171026104259.GA2179@thebird.nl> (raw)
In-Reply-To: <87mv4emlwf.fsf@elephly.net>
Hi Ricardo,
Thanks for responding. I think this discussion belongs here.
On Thu, Oct 26, 2017 at 09:02:56AM +0200, Ricardo Wurmus wrote:
>
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
>
> > 22M 3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib
>
> According to “du”, this is 32M on my disk. The “lib” subdir contains
> both shared libraries as well as ar archives for static linking;
> together they weigh in at 12MB. We may want to move them to a separate
> output.
Yes, I think that is what we should head for eventually. I vaguely
remember a discussion about this on this ML and people were against
separate outputs for doc, include, static-lib etc. What are you all
thinking now? Does it make sense to have the base package as small as
possible and split out the rest?
I know it is extra work.
> The package also contains lots of header files:
>
> 6.3M /gnu/store/3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib/lib/gcc/x86_64-unknown-linux-gnu/5.4.0/plugin/include/
>
> Not sure what to do with those without making the use of GCC a hassle.
Yes, that goes with gcc. No point keeping those separate.
> > 41M n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25
>
> This package still contains a lot of locale data. The directory
> “share/i18n/locales/” takes up 6.7M, and “share/locale” takes up another
> 4.3M. All the .a files under “lib” take up 8.7M.
>
> > 34M nnykzgwfy8mwh2gmxm715sjxykg8qjwn-binutils-2.28
>
> “share/locale” is 9.4M. This is a cross-cutting concern. We don’t have
> a way to globally filter locales to only requested locales. Even if we
> split them each into a separate output — how would you specify that you
> want the “de_DE” locale in each package and not install the rest?
Yes, it is a specific target discussion. Same goes for compilation
without debug information and optimizing for size. Tiny = tiny.
Ludo wrote at some point that target optimizations are on the roadmap.
It would be rather good to have. Maybe in the form of channels.
> There seems to be some duplication with these directories:
>
> /gnu/store/nnykzgwfy8mwh2gmxm715sjxykg8qjwn-binutils-2.28/x86_64-unknown-linux-gnu/bin/
> /gnu/store/nnykzgwfy8mwh2gmxm715sjxykg8qjwn-binutils-2.28/bin/
>
> But the binaries seem to be hardlinked, so they don’t take up extra
> space.
>
> > Now it takes forever to set up the image
>
> Have you tried disabling compression? This could be a lot faster. I
> found that tar with gzip compression is terribly slow to copy things
> from the store into a compressed tar archive. Disabling compression
> speeds this up considerably, even though it is still rather slow.
That will help :). But I was talking about Docker images. Making them
small would be helpful for a lot of people out there. It takes forever
to download and run Docker tests, for example, I hear people complain.
Pj.
next prev parent reply other threads:[~2017-10-26 10:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 8:18 Tiny Guix (and containers) Pjotr Prins
2017-10-25 11:12 ` Pjotr Prins
2017-10-26 7:02 ` Ricardo Wurmus
2017-10-26 10:42 ` Pjotr Prins [this message]
2017-10-26 10:48 ` Ricardo Wurmus
2017-10-27 8:25 ` Hartmut Goebel
2017-10-28 20:06 ` Ludovic Courtès
2017-10-31 14:17 ` Dave Love
2017-11-05 16:02 ` Ludovic Courtès
2017-11-06 15:45 ` Dave Love
2017-11-07 10:19 ` Ludovic Courtès
2017-10-27 0:35 ` Ludovic Courtès
2017-10-31 14:11 ` Dave Love
2017-11-03 12:08 ` Pjotr Prins
2017-11-06 15:10 ` Dave Love
2017-11-05 15:55 ` Ludovic Courtès
2017-11-06 15:11 ` Dave Love
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=20171026104259.GA2179@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).