all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 54852@debbugs.gnu.org
Subject: [bug#54852] [PATCH] gnu: Add openjdk18.
Date: Wed, 11 May 2022 20:22:25 +0200	[thread overview]
Message-ID: <6beb046093f8655ccfb67105800c93a5ce8259e5.camel@telenet.be> (raw)
In-Reply-To: <CAEtmmexbPzM1mwAkGJ_6_7ngixXQT7CUYKiH=UrQ9mA6jy+WdA@mail.gmail.com>

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

Rostislav Svoboda schreef op wo 11-05-2022 om 17:37 [+0200]:
> [env]$ time ./pre-inst-env guix build openjdk

Did you run this after it was already built, or before?  If the former,
it probably just counts time grafting (4min seems about accurate for
openjdk in my experience) due to some new grafts since last time.

For timing build times, I recommend:

# --no-grafts: don't do grafts to avoid counting time grafting
# --check --rounds=1: build it again
$ time ./pre-inst-env guix build openjdk --no-grafts --check --rounds=1

though that only does somethin usefu

> ...
> real 4m32.993s
> user 0m26.175s
> sys 0m1.357s

I compiled it with cores=1 or cores=4 or cores=8 (not sure which).
Since apparently you have a 24 core computer, multiplying by 24 would
give an estimate of 108m ≅ 2 hours for cores=1.  Though it ran much
longer than that on my computer (at least 12h), so I don't understand,
unless there was grafting involved.

I don't think it really matters though, so maybe we can drop this?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-05-11 18:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 12:53 [bug#54852] [PATCH] gnu: Add openjdk18 Rostislav Svoboda
2022-04-11 13:43 ` Maxime Devos
2022-04-12 13:03   ` Rostislav Svoboda
2022-04-11 13:44 ` Maxime Devos
2022-04-12 13:24   ` Rostislav Svoboda
2022-04-21 10:27     ` Rostislav Svoboda
2022-04-21 16:38       ` Maxime Devos
2022-04-22 10:59         ` Rostislav Svoboda
2022-04-23 14:38           ` Maxime Devos
2022-04-23 15:11             ` Rostislav Svoboda
2022-04-23 16:10               ` Maxime Devos
2022-04-11 14:15 ` Julien Lepiller
2022-04-13  7:51   ` Björn Höfling
2022-05-08 16:41 ` Maxime Devos
2022-05-09 19:11 ` Maxime Devos
2022-05-09 22:20   ` Rostislav Svoboda
2022-05-10  6:59     ` Maxime Devos
2022-05-11 15:37       ` Rostislav Svoboda
2022-05-11 18:13         ` Maxime Devos
2022-05-11 18:22         ` Maxime Devos [this message]
2022-05-11 18:30         ` Maxime Devos
2022-09-27 14:17         ` bug#54852: " Maxim Cournoyer

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=6beb046093f8655ccfb67105800c93a5ce8259e5.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54852@debbugs.gnu.org \
    --cc=rostislav.svoboda@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.