From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Typing latency
Date: Sat, 13 Feb 2021 22:49:21 +0700 [thread overview]
Message-ID: <s08se2$96n$1@ciao.gmane.io> (raw)
In-Reply-To: <87h7mitu9l.fsf@localhost>
On 11/02/2021 23:59, Ihor Radchenko wrote:
> Maxim Nikulin writes:
>
>> It is not namely typing latency, but I have noticed lags while moving
>> over collapsed headings with "up" key (with "down" it is not so
>> apparent) e.g. in overview view. It has happened after linux upgrade,
>> emacs version changed from 25.2 to 25.3, system package with org mode
>> updated as well. The org file has significant size: 50k lines, 2Mb. I
>> have created a LXC container to compare performance with older emacs. It
>> is quite strange. With org version from git, emacs version is not really
>> important, flyspell mode is irrelevant.
>
> You can try feature/org-fold branch aiming to address issues with
> performance on large files https://github.com/yantar92/org
Ihor, I have seen the thread with discussion of your branch. This case I
was surprised the simple move to next or previous currently displayed
line could be slow. I would expect that emacs has information (in some
internal structures) what position in the buffer is related to the same
x coordinate on the previous or next (visual) visible line. Ideally it
would not depend on how much text is hidden by overlays, properties,
etc. and should work instantly.
Update to my results. I suspected some problem with loader and I have
realized what actually had happened. I believed that -L (--directory)
emacs command line options have precedence and used the following command
emacs -L ~/org-mode/lisp test-file.org
actually -L processed after init.el file, so (require 'org-protocol) in
the init file loaded some files from org-9.1.6 (elpa-org system package)
then remaining files were loaded from git HEAD org version. Even
org-submit-bug-report did not worked, I tried it to get summary of
actual configuration. I do not run emacs in such way routinely, so the
problem was specific to my tests.
My current impression that in both cases of emacs-25.2 and 26.3, with
org from git moving cursor over collapsed headers works faster than with
org-9.1.6 or org-9.3.1 from elpa-org package. In all cases
line-move-visual dominates in profiler reports.
So slow down I have noticed is likely related to growth of the file size
rather than to system upgrade. I just mostly navigate through the file
using C-u C-c C-j, so I just was not using cursor keys in overview tree
display for some time.
So strange observation, due to that I sent previous message, is
explained: incorrect usage of command line option during tests. My
complains related to performance is not related to emacs upgrade, org
master branch HEAD from git works better. Maybe later I will try
suggestions how to improve performance or I will just split my file into
smaller parts.
Sorry for the noise.
prev parent reply other threads:[~2021-02-13 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 18:24 Typing latency Sébastien Miquel
2021-02-09 2:16 ` Russell Adams
2021-02-09 14:06 ` Sébastien Miquel
2021-02-09 3:23 ` Ihor Radchenko
2021-02-09 14:56 ` Sébastien Miquel
2021-02-09 15:33 ` Ihor Radchenko
2021-02-09 22:30 ` Sébastien Miquel
2021-02-10 3:38 ` Ihor Radchenko
2021-02-10 6:18 ` Timothy
2021-02-10 6:58 ` Ihor Radchenko
2021-02-10 8:56 ` Eric S Fraga
2021-02-10 23:09 ` Samuel Wales
2021-02-14 4:39 ` Timothy
2021-02-14 10:36 ` Eric S Fraga
2021-02-14 12:45 ` Timothy
2021-02-15 11:33 ` Eric S Fraga
2021-02-15 18:29 ` Sébastien Miquel
2021-02-26 19:58 ` [PATCH] ~org-font-lock-add-priority-faces~: ensure priority cookies are in a headline Sébastien Miquel
2021-03-02 5:10 ` Kyle Meyer
2021-02-09 9:38 ` Typing latency Eric S Fraga
2021-02-09 14:09 ` Sébastien Miquel
2021-02-09 14:23 ` Christian Thäter
2021-02-11 16:21 ` Eric S Fraga
2021-02-11 16:25 ` Maxim Nikulin
2021-02-11 16:59 ` Ihor Radchenko
2021-02-13 15:49 ` Maxim Nikulin [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
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='s08se2$96n$1@ciao.gmane.io' \
--to=manikulin@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 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).