emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Matt Lundin <mdl@imapmail.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Slow movement in large buffers
Date: Tue, 15 Mar 2011 10:58:32 +0000	[thread overview]
Message-ID: <87wrk0r6p3.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87d3ltjc8x.fsf@fastmail.fm> (Matt Lundin's message of "Mon, 14 Mar 2011 23:25:50 -0400")

Matt Lundin <mdl@imapmail.org> writes:

> I've been navigating the org-issues file (14000+ lines) and have found
> movement within the file to be fairly slow. Sometimes Emacs will lock up
> for several seconds.
>
> For instance, to move from the level one heading "* Other" to "* Closed
> issues" when the outline is folded takes over three seconds:
>
> next-line     1           3.015289      3.015289
>
> In my experience, the maximum workable size of org files is around
> 10,000 lines. Beyond that, Emacs starts to spin its wheels.
>
> Do others have the same experience? If so, does anyone have any tips on
> how to diagnose this further?
>
> (insert "\n" emacs-version)
> 23.3.1
>
> (insert "\n" org-version)
> 7.5
>
> Best,
> Matt
>
>  

Interesting.  It doesn't take 3 seconds on my system (Intel(R)
Pentium(R) D CPU 2.80GHz) but there is a noticeable delay using C-n to
move from =* Other= to =* Closed issues=.  However, using C-cC-n to move
has no delay at all and moving backwards (either C-p or C-cC-p) also
exhibits no delay.

I have noticed significant slowness in some of my own files lately when
including babel source code blocks, especially latex ones.  But I
haven't been able to reproduce this slowness predictably enough to
instrument it and hence report it in any useful sense... still
experimenting.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.38.gf8c6.dirty)

  parent reply	other threads:[~2011-03-15 10:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  3:25 Slow movement in large buffers Matt Lundin
2011-03-15  5:03 ` Carsten Dominik
2011-03-15 12:51   ` Matt Lundin
2011-03-15 10:58 ` Eric S Fraga [this message]
2011-03-15 12:54   ` Matt Lundin
2011-03-15 14:09     ` Eric S Fraga
2011-03-15 17:42       ` Carsten Dominik
2011-03-15 11:18 ` Carsten Dominik
2011-03-15 12:33   ` Lawrence Mitchell
2011-03-15 12:50   ` Matt Lundin
2011-03-15 14:15   ` Nick Dokos
2011-03-15 15:51     ` Matt Lundin
2011-03-15 17:39       ` Carsten Dominik
2011-03-15 22:00       ` Christian Moe
2011-03-15 22:56         ` Nick Dokos
2011-03-15 23:13           ` Christian Moe
2011-03-16  3:48             ` Nick Dokos
2011-03-16  1:16           ` Bastien
2011-03-18  0:37             ` Matt Lundin
2011-03-15 16:11 ` Chris Randle
2011-03-15 16:41   ` MidLifeXis at PerlMonks
2011-03-15 17:14   ` Scott Randby
2011-03-15 17:18     ` Erik Iverson
2011-03-15 17:38     ` Carsten Dominik
2011-05-11  0:41       ` Carmine Casciato
2011-05-12  6:59         ` Eric S Fraga

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=87wrk0r6p3.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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).