Re: follow-mode: extremely slow in combination with org-mode

[Gerald Wildgruber]

Hi Anders

thanks for your reply: I just returned to office and couldn't answer
earlier!

On Do, Jun 21 2018, Anders Lindgren <address@hidden> wrote:

>  Hi!
>
> There can be a number of reasons why follow-mode is slow. The main problem
> is that is it's time consuming to recompute the window state, and even more
> time consuming when aligning the windows. For simple commands like point
> movement, follow-mode assumes that the content of the buffers hasn't
> changed and retain the existing layout, whereas for other commands
> (including self-insert-command), everything is recomputed and realigned.
>
> However, I use six side by side windows, and a small font, giving me a
> total of almost 800 consecutive lines, and it typically runs fine without
> any noticeable lag.

That's quite close to my setup.

However: when I use org-mode, with entire branches collapsed, there
might well be several thousand (2000-15000) lines of text in the buffer;
if all this is recalculated every time I enter a letter, -- perhaps the
lags I observe are "normal". But then, the machine I'm working on is a
really fast and new computer.

> There are a number of factors that can have a negative impact on
> follow-mode:

> - It run slower on a 32 bit binary than on a 64 bit binary (at least under
> Windows). (For this reason, I used Emacs 22 at work for many years, until
> prebuilt 64 bit binaries of modern Emacs versions were available.)

Mine are 64 bit machines.

> - Follow-mode is has problems when the width of the windows differ,
> especially if you have long lines that spill over from one window to
> another. I've written a support package to set up side-by-side windows in a
> pixel-perfect way, https://github.com/Lindydancer/multicolumn -- please try
> if and see if follow-mode runs more smoothly.

Actually I use this already! I have in my .emacs the following:

(require 'multicolumn)
(multicolumn-global-mode 1)

> One thing that I have had on my wish-list for a very long time (20+ years)
> is that normal typing should use and update the cache, to speed things up.
> Of course, this only work as long as the editing doesn't change the layout,
> like when inserting a newline or make a line so long that it wraps.
> Unfortunately, I don't think that I will have time for it anytime soon, but
> I'm happy to share my ideas if someone else is willing to make a try.

I hope someone picks this up!!! :-)

Can you tell if the function that uses so much of cpu time --
follow-calc-win-end -- in the form it is now part of new emacs versions,
has any evident problem compared to your own longer version in pre
version 22 emacs? Cf Alan's posting in this thread:
https://lists.gnu.org/archive/html/emacs-devel/2018-06/msg00522.html

> What made me curious that you said that the slow-down only occurs with
> org-mode. My guess is that invisible text makes it harder for Emacs to
> calculate window layout properties.

Yes: the lag is much lower with text-mode.

Thanks again

Gerald.

> Sincerely,
>     Anders Lindgren (I wrote follow-mode when I was a student, in the mid
> 1990:s)
>
>
> On Sat, Jun 16, 2018 at 12:25 PM, Gerald Wildgruber <address@hidden
>> wrote:
>
>>
>> Hi,
>>
>> I have got a problem with enormous lag while entering text in buffers
>> with emacs follow-mode enabled.
>>
>> I'm using emacs (git checkout v. 27.0.50) and Org mode (git checkout
>> release_9.1.13-760-g8def68).
>>
>> My work is solely text-based, using org-mode. A typical setup is to use
>> a maximized or full screen emacs frame split into five windows
>> positioned vertically one next to the other on a 40" 4k display. All
>> five windows display one and the same file, that is opened using emacs
>> follow-mode, so that every window is displaying a portion of the same
>> file in a continuous manner (simultaneously displaying up to 45kb of
>> text in one frame, an entire paper).
>>
>> Unfortunately, with this setup there is terrible lag with every single
>> key input (on a very fast quad core machine); every key stroke produces
>> a 100% processor load.
>>
>> If I deactivate follow-mode, the problem disappears. It also gets better
>> if I enable text-mode instead of org-mode.
>>
>> I then used the elisp profiler (M-x profiler-start/report) to find out
>> which function uses most cpu time while editing text in said setup. Here
>> is the result:
>>
>> Collapsed, the report looks like that:
>>
>> + command-execute                                                8789  47%
>> + follow-post-command-hook                                       7755  41%
>> + ...                                                            1976  10%
>> + redisplay_internal (C function)                                 104   0%
>> + yas--post-command-handler                                        40   0%
>> + timer-event-handler                                              20   0%
>>   tooltip-hide                                                      7   0%
>>
>>
>> And somewhat expanded:
>>
>> - follow-post-command-hook                                       7755  41%
>>  - follow-adjust-window                                          7755  41%
>>   - follow-windows-start-end                                     7732  41%
>>    - follow-calc-win-end                                         7732  41%
>>     + pos-visible-in-window-p                                      25   0%
>>     + posn-at-x-y                                                   7   0%
>>     + window-inside-pixel-edges                                     3   0%
>>   + follow-all-followers                                            4   0%
>>     follow-avoid-tail-recenter                                      3   0%
>>
>> If I understand correctly "follow-calc-win-end" would be the function
>> that uses most of cpu time.
>>
>> I then did additional profiling with the elp library, adding relevant
>> functions under "Command-execute" and "follow-post-command-hook" to
>> elp-function-list, edited text, and then did M-x elp-results. It showed
>> again that "follow-calc-win-end" by far used most of cpu time.
>>
>> Anyone got an idea what's going on here and how to debug that? Are there
>> possible optimizations with this situation? Or is this "normal",
>> expected behavior, simply due to the number of windows and text
>> displayed?
>>
>> Thanks
>>
>> Gerald.
>>
>> ---------------------
>> Sent with mu4e
>>
>>


--
Dr. Gerald Wildgruber
Institut für Philosophie, Literatur-, Wissenschafts- und Technikgeschichte
Literaturwissenschaft mit Schwerpunkt Literatur und Wissenschaft
Technische Universität Berlin
Straße des 17. Juni 135
D-10623 Berlin
http://www.philosophie.tu-berlin.de/menue/home/
T. +49 (0)30 314 25924
F. +49 (0)30 314 23107
address@hidden
---------------------
Sent with mu4e