From: "Clément Lassieur" <clement@lassieur.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Estimating build time
Date: Sat, 13 Oct 2018 01:13:17 +0200 [thread overview]
Message-ID: <87a7ni3gj6.fsf@lassieur.org> (raw)
In-Reply-To: <87a7njgnsb.fsf_-_@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> In a similar vein, the attached module provides code to estimate package
> build time based on locally-available build logs. It can be used to
> show hints like this:
[...]
> The obvious downside is that it works by first retrieving the names of
> the files under /var/log/guix/drvs, and then opening, decompressing, and
> parsing the candidate log files. That typically takes a few seconds on
> a recent SSD laptop, but clearly we don’t want to do that every time.
> We could maintain a cache, but even then, it might still be too
> expensive.
>
> Perhaps we should keep build times in the database somehow; the daemon
> can keep it up-to-date.
>
> Thoughts?
>
> There’s the obvious downside that both approaches rely on having
> previously built the package, but I think that’s a necessary limitation,
> unless we are to resort to external services (which could hardly provide
> estimates that make sense for the user’s machine anyway.)
I think it's an excellent idea! I agree that the downside is necessary,
and yes, keeping the build times in the database sounds good!
Clément
next prev parent reply other threads:[~2018-10-12 23:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 13:18 hpcguix-web, channels, and inferiors Ludovic Courtès
2018-09-11 10:24 ` Pierre Neidhardt
2018-09-11 12:19 ` Ricardo Wurmus
2018-10-03 14:38 ` Clément Lassieur
2018-10-04 7:10 ` Ludovic Courtès
2018-10-04 17:34 ` Clément Lassieur
2018-10-05 9:15 ` Ludovic Courtès
2018-10-05 11:36 ` Ricardo Wurmus
2018-10-05 16:17 ` Ludovic Courtès
2018-10-11 19:20 ` Ricardo Wurmus
2018-10-12 15:58 ` Estimating build time Ludovic Courtès
2018-10-12 23:13 ` Clément Lassieur [this message]
2018-10-13 10:48 ` Pierre Neidhardt
2018-10-14 7:16 ` Efraim Flashner
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=87a7ni3gj6.fsf@lassieur.org \
--to=clement@lassieur.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.
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).