From: Ihor Radchenko <yantar92@gmail.com>
To: "andrés ramírez" <rrandresf@hotmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]
Date: Thu, 22 Sep 2022 12:44:34 +0800 [thread overview]
Message-ID: <CACnOyih6aReSOZ5vC1HDL2j54tNEVWHXnz+0HQ83Fg_ohjgnrg@mail.gmail.com> (raw)
In-Reply-To: <SJ1PR12MB6363E1A973EEAB02272A6293A64E9@SJ1PR12MB6363.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
>
> Ihor> Can you: 1. Load your agenda 2. Start 'cpu+mem profiler 3.
> Rebuild the agenda 4. Share the
> Ihor> obtained 'cpu _and_ 'mem reports
>
> I found an issue.
> --8<---------------cut here---------------start------------->8---
> void-function org-looking-at
> --8<---------------cut here---------------end--------------->8---
>
Oops. Fixed.
> Ihor> native-comp is improving things proportionally. It should
> actually have higher impact on
> Ihor> lower-end machine. I recommend native-comp unless you update
> frequently (and hence need to
> Ihor> re-compile using native-comp often).
>
> On my case. My distro which is archlinux-arm aka alarm for 32bits does
> not provide the compiled package libgccjit. So compiling it takes
> several hours on this little machine. cross-compiling it takes almost
> 1h, but preparing the machine for cross-compilation takes time also. So
> my conclusion is 'it does not worth the hassle'.
>
Makes sense.
If you want to squeeze maximum out of Emacs startup and do not update
frequently, you may look into
https://archive.casouri.cat/note/2020/painless-transition-to-portable-dumper/index.html
Best,
Ihor
[-- Attachment #2: Type: text/html, Size: 1797 bytes --]
next prev parent reply other threads:[~2022-09-22 4:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 17:02 [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)] Andrés Ramírez
2022-09-08 5:59 ` Ihor Radchenko
2022-09-12 17:55 ` andrés ramírez
2022-09-13 1:56 ` Ihor Radchenko
2022-09-13 2:53 ` andrés ramírez
2022-09-13 3:03 ` Ihor Radchenko
2022-09-13 4:00 ` andrés ramírez
2022-09-13 4:45 ` Ihor Radchenko
2022-09-13 23:29 ` andrés ramírez
2022-09-14 2:15 ` Ihor Radchenko
2022-09-14 16:30 ` andrés ramírez
2022-09-16 4:35 ` Ihor Radchenko
2022-09-16 11:31 ` andrés ramírez
2022-09-20 11:30 ` Ihor Radchenko
2022-09-20 13:28 ` andrés ramírez
2022-09-20 13:51 ` Ihor Radchenko
2022-09-20 14:51 ` andrés ramírez
2022-09-21 4:47 ` Ihor Radchenko
2022-09-22 1:59 ` andrés ramírez
2022-09-22 3:32 ` Ihor Radchenko
2022-09-22 4:27 ` andrés ramírez
2022-09-22 4:44 ` Ihor Radchenko [this message]
2022-09-22 5:00 ` andrés ramírez
2022-09-22 5:04 ` Ihor Radchenko
2022-09-22 13:23 ` andrés ramírez
2022-09-23 3:05 ` Ihor Radchenko
2022-09-23 3:19 ` andrés ramírez
2022-09-23 3:35 ` Ihor Radchenko
2022-09-23 3:57 ` andrés ramírez
2022-09-23 5:11 ` Ihor Radchenko
2022-09-23 14:55 ` andrés ramírez
2022-09-23 15:36 ` Ihor Radchenko
2022-09-23 16:14 ` andrés ramírez
2022-09-23 17:08 ` Fraga, Eric
2022-09-23 17:23 ` andrés ramírez
2022-09-24 3:20 ` Ihor Radchenko
2022-09-24 4:10 ` on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]) andrés ramírez
2022-09-24 4:34 ` Ihor Radchenko
2022-09-26 16:37 ` andrés ramírez
2022-09-27 2:38 ` Ihor Radchenko
2022-09-27 2:59 ` on picking diary-style timestamps or normal timestamps when adding agenda entries andrés ramírez
2022-09-27 3:21 ` Ihor Radchenko
2022-09-23 16:33 ` [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)] Max Nikulin
2022-09-24 3:28 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACnOyih6aReSOZ5vC1HDL2j54tNEVWHXnz+0HQ83Fg_ohjgnrg@mail.gmail.com \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rrandresf@hotmail.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/emacs/org-mode.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).