unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Slow/poor responsiveness in org files
Date: Thu, 18 Aug 2011 09:49:10 +0200	[thread overview]
Message-ID: <87fwkzcg7d.fsf@gnu.org> (raw)
In-Reply-To: <CAC=50j9SbZ2kTm_MoZZEr6DQ8yKbZgFbm1riNaMe73=oeUDZPw@mail.gmail.com> (Tim Cross's message of "Thu, 18 Aug 2011 15:56:04 +1000")

Hi Tim,

Tim Cross <theophilusx@gmail.com> writes:

> About a week or so ago, I updated emacs from bzr and saw that org 7.7
> had been merged in. Since then, I have also noticed a distinct delay
> when performing various editing operations within org files. For
> example, killing a line wiht C-k in an org mode buffer is taking about
> 4 seconds!

This might come either from Org and/or from Emacs.

> I updated emacs and tried again with emacs -Q and got the same result
>
> My version is 24.0.50 bzr relno 105475
>
> Has anyone else seen this? 

Yes.

> What would be the best way to debug this sort of issue, emacs
> profiler?

Four tests would be useful:

- Emacs 23 + Org 7.4
- Emacs 23 + Org 7.7
- Emacs 24 (from trunk) + Org 7.4
- Emacs 24 (from trunk) + Org 7.7

For each case, M-x elp-instrument-package RET org-mode RET to
see if there is any particular function that takes significantly
more time.  

I'm busy fixing small bugs in Org 7.7 but fixing such slowniness
is high priority and such tests would really help me *a lot*.

Thanks in advance!

-- 
 Bastien



  reply	other threads:[~2011-08-18  7:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  5:56 Slow/poor responsiveness in org files Tim Cross
2011-08-18  7:49 ` Bastien [this message]
2011-08-18 11:53   ` Antoine Levitt
2011-08-19 23:42     ` Tim Cross
2011-08-20  0:23       ` Bastien
2011-08-20  0:53         ` Tim Cross
2011-08-22  0:52           ` Tim Cross
2011-08-22  5:55             ` Eli Zaretskii
2011-08-22  6:42               ` Tim Cross
2011-08-22  7:03                 ` Eli Zaretskii
2011-09-13  0:22               ` Mathieu Boespflug
2011-09-13  2:59                 ` Eli Zaretskii
2011-09-13  4:36                   ` Mathieu Boespflug
2011-09-13  5:51                     ` Eli Zaretskii
2011-09-14 15:34                       ` Paragraph direction in Org Mode (was: Slow/poor responsiveness in org files) Eli Zaretskii
2011-09-20 15:02                         ` Eli Zaretskii
2011-09-13 16:55                     ` Slow/poor responsiveness in org files Bruno Tavernier
2011-09-14 15:37                       ` Eli Zaretskii
2011-09-14 18:00                         ` Bruno Tavernier
2011-09-14 19:55                           ` Eli Zaretskii
2011-09-13 20:42             ` Claus Klingberg
2011-09-14  3:01               ` Eli Zaretskii
2011-09-13  3:20 ` Torsten Wagner
2011-09-13  4:52   ` Tim Cross

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=87fwkzcg7d.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-devel@gnu.org \
    --cc=theophilusx@gmail.com \
    /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).