unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Slow generation of Org manual
Date: Sat, 29 Jun 2024 19:25:31 +0300	[thread overview]
Message-ID: <86frsviumc.fsf@gnu.org> (raw)
In-Reply-To: <87y16ng4wi.fsf@localhost> (message from Ihor Radchenko on Sat, 29 Jun 2024 15:11:41 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: emacs-devel@gnu.org
> Date: Sat, 29 Jun 2024 15:11:41 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The generation of the Org manual from org.org on the master branch is
> > again taking a long time.  On one system I use (which is relatively
> > slow), it takes a whopping 4.5 min.  On a much faster system it still
> > takes more than 20 sec.
> >
> > Can this be sped-up, please?
> 
> I do not think that it has anything to do with Org.
> I also observed slow generation of the manual on master, but it was a
> result of Org manual being generated _before_ Org mode is compiled.

That's not what I see here.  Org is already byte-compiled when the Org
manual is generated.  So this cannot be the reason.

> If I do
> 
> time (touch doc/misc/org.org && make)
> 
> _after_ full compilation, I am getting
> 
> real	0m10.850s
> user	0m10.548s
> sys	0m0.293s

I'm guessing this is on a fast machine, in an optimized build, and
probably also with native compilation, right?

> This is the usual time I saw in the earlier versions, after we bumped
> the gc-cons-threshold.

Which earlier versions?  Does that include Emacs 29?

Anyway, something has clearly changed, since it never took so long,
AFAIR.  Did the Org manual in the version that is now on the emacs-30
branch change significantly wrt what we had in Emacs 29?



  reply	other threads:[~2024-06-29 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-29 14:31 Slow generation of Org manual Eli Zaretskii
2024-06-29 15:11 ` Ihor Radchenko
2024-06-29 16:25   ` Eli Zaretskii [this message]
2024-06-29 16:33     ` Ihor Radchenko

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86frsviumc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@posteo.net \
    /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/emacs.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).