From: Visuwesh <visuweshm@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-persist-write-all is slow because of use of pp [9.8-pre (release_9.7.8-713-g62cbac @ /home/viz/lib/emacs/straight/build/org/)]
Date: Sat, 10 Aug 2024 10:40:25 +0530 [thread overview]
Message-ID: <87r0axvu7y.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
I am using the async LaTeX preview branch and org-persist-write-all
takes a lot of time to finish executing due to the use of pp when saving
the index file. Changing org-persist-write:index to not pass a non-nil
PP argument to org-persist--write-elisp-file changes the execution time
of org-persist-write-all from 62 secs to just 8 secs. For reference,
(length org-persist--index) ;; ⇒ 1504
I have attached the profiler report for org-persist--index of much
smaller length but if required I can reproduce a report for the full one
too.
Please let me know if more information is required from my side. Thank
you.
[-- Attachment #2: org-persist-pp-slow-down.eld --]
[-- Type: application/octet-stream, Size: 373477 bytes --]
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
Emacs : GNU Emacs 31.0.50 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo version 1.18.0, Xaw scroll bars)
of 2024-08-10
Package: Org mode version 9.8-pre (release_9.7.8-713-g62cbac @ /home/viz/lib/emacs/straight/build/org/)
next reply other threads:[~2024-08-10 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 5:10 Visuwesh [this message]
2024-08-10 12:48 ` [BUG] org-persist-write-all is slow because of use of pp [9.8-pre (release_9.7.8-713-g62cbac @ /home/viz/lib/emacs/straight/build/org/)] Ihor Radchenko
2024-08-10 13:07 ` Visuwesh
2024-08-10 13:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0axvu7y.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=emacs-orgmode@gnu.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.