unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "44053@debbugs.gnu.org" <44053@debbugs.gnu.org>
Subject: bug#44053: Poor profile generation performance on spinning disks
Date: Sun, 18 Oct 2020 23:05:10 +0000	[thread overview]
Message-ID: <yuID-gVO5clS0T8k81R_AzM7g91lm_6kDlH9rJFE8OOv5XMxEsdFo6hCH_QGnJGMW4nyDfuduHS_cXzKOm0qov8BalGmi8NPGKwR_eInGFk=@protonmail.com> (raw)
In-Reply-To: <87zh4k435a.fsf@gmail.com>

I've never used SDDs, so I've been experiencing this since I installed Guix (~5 years ago). And yes, building the profile seems to be the more resource intensive operation. I usually can't do anything else while that happens because the computer becomes unresponsive.

Running the same command Maxim mentioned took the following time in my case:


$ time guix package -i perl --max-jobs=1
Se instalará el siguiente paquete:
   perl 5.30.2
Se construirá la siguiente derivación:
   /gnu/store/86g48nh8dhgdhzb8r9bxjk6mmszlssss-profile.drv
construyendo empaquetado de certificados de CA...
construyendo el directorio de tipografías...
generando la caché de esquemas de GLib...
creando la caché de temas de iconos de GTK+...
construyendo los ficheros de caché para los métodos de entrada de GTK+...
construyendo el directorio de manuales Info...
construyendo la base de datos de páginas de manual...
construyendo la caché de ficheros desktop XDG...
construyendo la base de datos MIME XDG...
construyendo perfil con 87 paquetes...


real    8m3,043s
user    0m2,656s
sys    0m0,239s


My computer:

Intel® Core™ i3-8100 CPU @ 3.60GHz × 4
RAM: 4 GiB
1 TB HDD





  reply	other threads:[~2020-10-18 23:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18  3:35 bug#44053: Poor profile generation performance on spinning disks Maxim Cournoyer
2020-10-18 23:05 ` Luis Felipe via Bug reports for GNU Guix [this message]
2020-10-19  8:18 ` zimoun
2020-10-19 18:18   ` Maxim Cournoyer
2022-03-23 12:38 ` zimoun
2022-03-23 16:17   ` Maxim Cournoyer
2022-03-23 16:54     ` zimoun
2023-08-26 22:11 ` jbranso--- via Bug reports for GNU Guix
2023-08-27 17:59   ` Luis Felipe via Bug reports for GNU Guix
2023-08-29  9:19     ` Ludovic Courtès
2023-08-29 21:51       ` Luis Felipe via Bug reports for GNU Guix
2023-09-09 11:02         ` Ludovic Courtès

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='yuID-gVO5clS0T8k81R_AzM7g91lm_6kDlH9rJFE8OOv5XMxEsdFo6hCH_QGnJGMW4nyDfuduHS_cXzKOm0qov8BalGmi8NPGKwR_eInGFk=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=44053@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.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 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).