all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Emmanuel Beffara <manu@beffara.org>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: performance issue with TeX Live
Date: Sat, 14 Oct 2023 12:06:34 -0400	[thread overview]
Message-ID: <878r852np1.fsf@gmail.com> (raw)
In-Reply-To: <20231009111109.GH1344@beffara.org> (Emmanuel Beffara's message of "Mon, 9 Oct 2023 11:11:09 +0200")

Hi,

Emmanuel Beffara <manu@beffara.org> writes:

> 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.

Have you tried tracing execution with strace?  Maybe try 'strace -e
file -f -s800 $texlive-cmd' and confirm whether the ls-R file gets used;
if it does, you could then introspect said file to see if it provides
what is being looked up or not.

-- 
Thanks,
Maxim


  parent reply	other threads:[~2023-10-14 16:07 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=878r852np1.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=manu@beffara.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 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.