From: Eli Zaretskii <eliz@gnu.org>
To: Gerald Wildgruber <wildgruber@tu-berlin.de>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: follow-mode: extremely slow in combination with org-mode
Date: Sun, 17 Jun 2018 18:10:49 +0300 [thread overview]
Message-ID: <83d0wptpmu.fsf@gnu.org> (raw)
In-Reply-To: <87tvq1qx6n.fsf@tu-berlin.de> (message from Gerald Wildgruber on Sun, 17 Jun 2018 16:56:00 +0200)
> From: Gerald Wildgruber <wildgruber@tu-berlin.de>
> CC: Alan Mackenzie <acm@muc.de>, <emacs-devel@gnu.org>
> Date: Sun, 17 Jun 2018 16:56:00 +0200
>
> I byte compiled the patched follow.el restarted emacs and began editing.
>
> It actually seems somewhat faster, though not enormously;
If the speedup is not significant, then I guess there are other
factors at work, although the profile seemed to show I was eliminating
the hottest function calls.
> I will continue working with this patched version to see how it
> goes; I have a more problematic (=slower) machine in my office, and
> I'm am eager to see, if it makes a difference there; at home, where
> I'm testing right now, its a new quad core xeon with 64gb of ram, --
> and it is kind of strange that with such a machine fans start very
> audibly as soon as you start TYPING (not video editing or the like)
> :-)
Each character you insert triggers redisplay, and I'm guessing
follow-mode has many of the redisplay optimizations disabled. But it
may be interesting to see a profile when all you do is type
self-inserting characters, maybe we will learn something important
from that.
> One more observation: it might be that the slowing down becomes more
> noticeable, the closer point gets to the bottom of the last window
> (lower right edge of my five-fold splitted emacs frame), but I couldn't
> reproduce this consistently.
This could be due to follow-calc-win-start, which loops over windows.
Or maybe there's another loop. Again, a profile might tell something
interesting.
> Please count on me for any other testing that might be necessary! I'm no
> programmer but will do my best to deliver usable results.
>
> Here's how the profile looks now, with the patched, uncompiled follow.el
> loaded right before profiling:
Thanks.
next prev parent reply other threads:[~2018-06-17 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 10:25 follow-mode: extremely slow in combination with org-mode Gerald Wildgruber
2018-06-16 11:41 ` Eli Zaretskii
2018-06-16 13:06 ` Gerald Wildgruber
2018-06-16 16:25 ` Eli Zaretskii
2018-06-16 21:05 ` Gerald Wildgruber
2018-06-17 6:57 ` Gerald Wildgruber
2018-06-17 8:12 ` Eli Zaretskii
2018-06-17 11:13 ` Alan Mackenzie
2018-06-17 13:02 ` Eli Zaretskii
2018-06-17 14:56 ` Gerald Wildgruber
2018-06-17 15:10 ` Eli Zaretskii [this message]
2018-06-19 12:08 ` Gerald Wildgruber
2018-06-19 16:55 ` Eli Zaretskii
2018-06-19 13:53 ` Gerald Wildgruber
2018-06-17 15:13 ` Eli Zaretskii
2018-06-21 8:25 ` Anders Lindgren
2018-06-27 16:43 ` Gerald Wildgruber
2018-07-09 20:12 ` Anders Lindgren
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d0wptpmu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=wildgruber@tu-berlin.de \
/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.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).