unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Fast `guix environment --container' switch
Date: Wed, 09 Dec 2020 12:47:29 +0100	[thread overview]
Message-ID: <86czzji4ku.fsf@gmail.com> (raw)
In-Reply-To: <87lfe72qq6.fsf@ambrevar.xyz>

On Wed, 09 Dec 2020 at 11:55, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> `guix environment` incurs an overhead:
>
> --8<---------------cut here---------------start------------->8---
> time /gnu/store/a462kby1q51ndvxdv3b6p0rsixxrgx1h-hello-2.10/bin/hello
> Hello, world!
>
> real	0m0.002s
> user	0m0.002s
> sys	0m0.000s
> --8<---------------cut here---------------end--------------->8---
>
> --8<---------------cut here---------------start------------->8---
> $ time guix environment --ad-hoc hello -- hello
> Hello, world!
>
> real	0m0.921s
> user	0m1.003s
> sys	0m0.091s
> --8<---------------cut here---------------end--------------->8---
>
> It's possible to bypass this overhead by using --root:

It by-passes the computations of derivations and profiles.  Somehow,
using --root is using a precomputed profile. IIUC.

> So is it possible to use a similar trick to run something containerized
> "instantly", i.e.  with less than, say, 100ms overhead?

I see, you would like to be able to run a profile in container, right?
Somehow, it is similar to the wanted [1], IIUC.

1: <https://yhetil.org/guix-devel/877dvn10ro.fsf@dustycloud.org>


Cheers,
simon


  reply	other threads:[~2020-12-09 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  9:40 Fast `guix environment --container' switch Pierre Neidhardt
2020-12-09 10:07 ` zimoun
2020-12-09 10:13   ` Pierre Neidhardt
2020-12-09 10:37     ` zimoun
2020-12-09 10:55       ` Pierre Neidhardt
2020-12-09 11:47         ` zimoun [this message]
2020-12-09 12:02           ` Pierre Neidhardt
2020-12-17 21:52 ` Ludovic Courtès
2020-12-29 21:47   ` Pierre Neidhardt
2021-01-05 22:50   ` Christopher Lemmer Webber
2021-01-26 10:31   ` Pierre Neidhardt

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=86czzji4ku.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).