unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emmanuel Beffara <manu@beffara.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: performance issue with TeX Live
Date: Mon, 9 Oct 2023 11:11:09 +0200	[thread overview]
Message-ID: <20231009111109.GH1344@beffara.org> (raw)
In-Reply-To: <87v8cetfgd.fsf@nicolasgoaziou.fr>

Hello,

De Nicolas Goaziou le 13/09/2023 à 14:39:
> Emmanuel Beffara <manu@beffara.org> writes:
> 
> > I am facing a severe performance issue with TeX Live: compilation of any
> > document is an order of magnitude slower with a Guix installed system as
> > compared to a manual installation. Is anyone confronted to this phenomenon, or
> > is there a way to fix this ?
> 
> I also experienced a noticeable slowdown; I don't know how to fix it yet.
[...]
> A ls-R file is generated during profile creation (see
> `texlive-font-maps' function in "guix/profiles.scm") but it seems it is
> not read.
> 
> It may be interesting to compare location and contents of the ls-R files
> in both installations.

I tried to explore this but I see no reason why the ls-R files would be
ignored and I don't know how to explore this further. I do want to contribute
to a solution, because right now texlive is practically unusable in Guix.

-- 
Emmanuel


  reply	other threads:[~2023-10-09  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 15:54 performance issue with TeX Live Emmanuel Beffara
2023-09-12 17:11 ` Olivier Dion
2023-09-13 12:42   ` Emmanuel Beffara
2023-09-13 12:39 ` Nicolas Goaziou
2023-10-09  9:11   ` Emmanuel Beffara [this message]
2023-10-09 14:03     ` Nicolas Goaziou
2023-10-10  8:04       ` Emmanuel Beffara
2023-10-11 16:16         ` Ricardo Wurmus
2023-10-14 16:06     ` Maxim Cournoyer
2023-10-16 12:22       ` Emmanuel Beffara
2023-10-16 13:46         ` Maxim Cournoyer
2023-10-16 15:16           ` Emmanuel Beffara
2023-10-16 16:23             ` 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

  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=20231009111109.GH1344@beffara.org \
    --to=manu@beffara.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).