unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gerald Wildgruber <wildgruber@tu-berlin.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: follow-mode: extremely slow in combination with org-mode
Date: Sun, 17 Jun 2018 08:57:22 +0200	[thread overview]
Message-ID: <877emx3not.fsf@tu-berlin.de> (raw)
In-Reply-To: <838t7ezokb.fsf@gnu.org>


On Sa, Jun 16 2018, Eli Zaretskii <eliz@gnu.org> wrote:

> There's something here I don't understand.  This profile says that
> follow-calc-win-end calls posn-point via two 'apply' calls, a
> byte-compiled function, and a lambda-function.  But there's nothing
> like that in follow.el that I could see.  Did you advise some
> functions in follow.el?  If not, what are those intermediate calls?

I repeated the profiling two times; the intermediate calls disappeared;
I can't say what might have caused them; here is the result:

- follow-post-command-hook                                      21938  71%
 - if                                                           21938  71%
  - let                                                         21938  71%
   - save-current-buffer                                        21938  71%
    - follow-adjust-window                                      21933  71%
     - if                                                       21933  71%
      - progn                                                   21933  71%
       - let                                                    21906  71%
        - let*                                                  21906  71%
         - progn                                                17609  57%
          - follow-windows-start-end                            17606  57%
           - if                                                 17606  57%
            - let                                               17603  57%
             - let                                              17603  57%
              - while                                           17603  57%
               - setq                                           17599  57%
                - cons                                          17599  57%
                 - cons                                         17599  57%
                  - cons                                        17599  57%
                   - follow-calc-win-end                        17591  57%
                    - let*                                      17591  57%
                     - if                                        9229  30%
                      + let                                      1115   3%
                      + pos-visible-in-window-p                    26   0%
                       posn-point                                8350  27%
                     + window-inside-pixel-edges                   12   0%
            + follow-cache-valid-p                                  3   0%
          + follow-update-window-start                              3   0%
         - if                                                    4297  13%
          - follow-redisplay                                     3329  10%
           - let*                                                3329  10%
            - cond                                               2924   9%
             - follow-calculate-first-window-start-from-above               2924   9%
              - save-excursion                                   2924   9%
               - let                                             2924   9%
                - while                                          2924   9%
                 - if                                            2924   9%
                  - setq                                         2899   9%
                   - follow-calc-win-start                       2899   9%
                    - while                                      2899   9%
                     - let                                       2899   9%
                      - setq                                     2896   9%
                       - car                                     2896   9%
                        - follow-calc-win-end                    2896   9%
                         - let*                                  2896   9%
                            posn-point                           1455   4%
                            if                                   1441   4%
                        set-window-start                            3   0%
                  + not                                            25   0%
            + let                                                 169   0%
            + follow-calc-win-start                               125   0%
            + follow-estimate-first-window-start                  111   0%
          + let                                                   598   1%
          + setq                                                  364   1%
          + follow-avoid-tail-recenter                              3   0%
          + and                                                     3   0%
       + follow-avoid-tail-recenter                                27   0%
      set-buffer                                                    5   0%


>> > If you "show all" in the Org buffer, do the lags become significantly
>> > smaller?
>>
>> Yes, the difference is VERY significant; but I guess this is because
>> with collapsed headings, there is A LOT more text within the boundaries
>> of my frame, than with show-all.
>
> How much is "A LOT more"?  How many physical lines do you have in
> typical single window in that Org buffer?

When I do a SHOW-ALL, my emacs frame split into those five windows
connected by follow-mode show about 700 lines of (natural language)
text. If COLLAPSED, it can be up to several thousand lines of text
hidden under the org headings (typically two to ten thousand lines).

Gerald.

---------------------
Sent with mu4e



  parent reply	other threads:[~2018-06-17  6:57 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 [this message]
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
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=877emx3not.fsf@tu-berlin.de \
    --to=wildgruber@tu-berlin.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.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).