emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: mail@christianmoe.com
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode <emacs-orgmode@gnu.org>,
	nicholas.dokos@hp.com,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: Slow movement in large buffers
Date: Tue, 15 Mar 2011 18:56:53 -0400	[thread overview]
Message-ID: <6135.1300229813@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Christian Moe <mail@christianmoe.com> of "Tue, 15 Mar 2011 23:00:15 BST." <4D7FE16F.10305@christianmoe.com>

Christian Moe <mail@christianmoe.com> wrote:

> 
> > Yes, hardware is indeed a factor here. I'm using a dual-core Atom processor
> > with 2GB of memory.
> >
> > Matt
> >
> 
> I'm not so sure about the hardware factor.
> 
> I'm on a seven-year-old G4 Mac PPC laptop with 768 MB RAM.
> 
> Over the same folded headings in a freshly pulled org-issues (Other to
> Development Tasks), I get
> 
> previous-line      5       5.89456       1.178912
> 
> Definitely a lag, but not as bad as you're seeing.
> 
> 

True, but it's still a factor: on my laptop I get

--8<---------------cut here---------------start------------->8---
previous-line  2           1.435139      0.7175695
next-line      1           0.446293      0.446293
--8<---------------cut here---------------end--------------->8---

being very careful to avoid next-line/previous-line in any other
context:  that was one next-line from "Other" to "Closed issues" and two
previous-lines from "Closed Issues" to "Other" to "Development
Tasks". Given the five previous-lines in your profile, I suspect that
one or two were much longer than the others which skewed the average.

Given the evidence that Lawrence Mitchell provided however, it seems clear
that most of the blame can be placed on overlays - no?

Nick

  reply	other threads:[~2011-03-15 22:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  3:25 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
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 [this message]
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=6135.1300229813@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    --cc=mdl@imapmail.org \
    --subject='Re: Re: Slow movement in large buffers' \
    /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

Code repositories for project(s) associated with this 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).