all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Troy Sankey <sankeytms@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: hydra queue length
Date: Thu, 31 Aug 2017 18:05:28 +0100	[thread overview]
Message-ID: <20170831180528.44751a5d@cbaines.net> (raw)
In-Reply-To: <150419804110.9803.6413741840234954697@x220>

[-- Attachment #1: Type: text/plain, Size: 1996 bytes --]

On Thu, 31 Aug 2017 12:47:21 -0400
Troy Sankey <sankeytms@gmail.com> wrote:

> I use Guix on an old thinkpad, and I've noticed that every time I run
> `guix pull` followed by `guix package -u`, I need to compile many of
> the packages.  That whole process could take about an hour on my
> laptop (compiling the package definitions, and many of the package
> upgrades in my profile).  I usually also have to close all my Firefox
> processes to free up memory.  On a weekly basis, I basically need to
> give up my laptop to guix for an hour.
> 
> My assumption is that this is due to the massive Hydra queue length.
> Hydra is so over-worked that many of the jobs get delayed for multiple
> days.  As of this writing, 2 of the 7 jobs currently running on Hydra
> were queued 2 and 3 days ago.
> 
> Is that a correct assumption?  If so, should I just be waiting 2 days
> between `guix pull` and `guix package -u`?  Is there some development
> work lined up to reduce the queue length, or is the Guix project just
> in need of more money to add machines to the build farm?

I think there is lots of room for improvement in this general area,
but, initially, you might want to try a few things, and see if they
improve your experience.

Firstly, try using `guix package --dry-run -u` or possibly `guix
weather` [1] if you have a manifest, as I think both of these commands
give some information about how much building guix package -u would
do, if you were to run it.

1: https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00288.html

Secondly, there are 3 main substitute servers that I know of: hydra,
bayfront, and berlin. You might want to check which ones you are using,
as adding more should increase the chance that you get substitutes
rather than building from source. There is some information about the
berlin substitute servers here [2].

2: https://lists.gnu.org/archive/html/guix-devel/2017-08/msg00128.html

Let us know how you get on :)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2017-08-31 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 16:47 hydra queue length Troy Sankey
2017-08-31 17:05 ` Christopher Baines [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170831180528.44751a5d@cbaines.net \
    --to=mail@cbaines.net \
    --cc=help-guix@gnu.org \
    --cc=sankeytms@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.