From: Ihor Radchenko <yantar92@gmail.com>
To: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: opening a 0.5 MB org file is slow
Date: Thu, 01 Oct 2020 16:44:18 +0800 [thread overview]
Message-ID: <87y2kqnxnh.fsf@localhost> (raw)
In-Reply-To: <87sgayxrqy.fsf@mat.ucm.es>
> + redisplay_internal (C function) 1724 82%
> Not sure what to do with stuff on the C level.
Look inside that branch. Most likely redisplay is calling font-lock
staff. You need to check what particular part of fontification is slow.
Best,
Ihor
Uwe Brauer <oub@mat.ucm.es> writes:
>>>> "JJ" == Jeremie Juste <jeremiejuste@gmail.com> writes:
>
>> Hello Uwe,
>> Very well, it seems that we are on the right track. So you might gain
>> some speed by preventing some minor modes to load at the beginning and
>> load only when you need them.
>
>> Like Ihor Radchenko mentioned in his previous a great way to diagnose
>> the issu would be the following:
>
>> 1. M-x profiler-start cpu
>> 2. open your file
>> 3. M-x profiler-report
>
>> It will let you see which functions are slowing you down.
>
> Thanks! I did it. But I am a bit puzzled about the outcome:
>
> + redisplay_internal (C function) 1724 82%
> + command-execute 215 10%
> + ... 117 5%
> + timer-event-handler 22 1%
> global-orglink-mode-check-buffers 1 0%
>
> Not sure what to do with stuff on the C level.
>
> Uwe
prev parent reply other threads:[~2020-10-01 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 19:11 opening a 0.5 MB org file is slow Uwe Brauer
2020-09-29 21:06 ` Jeremie Juste
2020-09-29 21:48 ` Russell Adams
2020-09-30 4:12 ` Ihor Radchenko
2020-09-30 4:35 ` Samuel Wales
2020-09-30 5:01 ` TEC
2020-09-30 5:13 ` Ihor Radchenko
2020-09-30 22:33 ` Jeremie Juste
2020-09-30 19:13 ` Uwe Brauer
2020-09-30 16:37 ` Eric S Fraga
2020-09-30 19:10 ` Uwe Brauer
2020-09-30 22:27 ` Jeremie Juste
2020-10-01 8:41 ` Uwe Brauer
2020-10-01 8:44 ` Ihor Radchenko [this message]
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=87y2kqnxnh.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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.