From: Nick Dokos <nicholas.dokos@hp.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode <emacs-orgmode@gnu.org>,
nicholas.dokos@hp.com
Subject: Re: Slow movement in large buffers
Date: Tue, 15 Mar 2011 10:15:47 -0400 [thread overview]
Message-ID: <7205.1300198547@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Carsten Dominik <carsten.dominik@gmail.com> of "Tue, 15 Mar 2011 12:18:51 BST." <17242340-A14F-495A-B144-20C96D52B620@gmail.com>
Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
> On Mar 15, 2011, at 4:25 AM, Matt Lundin wrote:
>
> > 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:
> >
> > --8<---------------cut here---------------start------------->8---
> > next-line 1 3.015289 3.015289
> > --8<---------------cut here---------------end--------------->8---
> >
>
> Wow, this is really bad.
> Could you use elp and instrument org, outline,
> and font-lock, and do that motion and report
> the results?
>
> > In my experience, the maximum workable size of org files is around
> > 10,000 lines. Beyond that, Emacs starts to spin its wheels.
>
> Not good at all.
>
> - Carsten
>
> >
> > 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
> >
FWIW, I opened org-issues.org and followed Matt's lead: at first, I got
almost instant response going from Other to Closed (using arrow-down)
and a slight hesitation (< 0.5s) going from Other to the previous
headline (Development Tasks). After noodling around for a while
(including the motions that Eric F. suggested and getting no delays
there), I tried it again and could discern no delay going either
way. And I do run flyspell in org buffers.
This is on a fairly recent vintage laptop with an i7 quad core processor
(2.67GHz) and 4G of memory. That probably explains some of the difference
I see. Matt, what kind of hardware are you using?
Nick
next prev parent reply other threads:[~2011-03-15 14:16 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
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 [this message]
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=7205.1300198547@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=carsten.dominik@gmail.com \
--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).