emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Why navigating in Org mode is so slow in overview mode?
Date: Tue, 23 Jun 2015 12:49:21 +0200	[thread overview]
Message-ID: <20150623104921.GA6709@boo.workgroup> (raw)
In-Reply-To: <87k2ux5sq3.fsf@selenimh.access.network>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

Hi Nicolas,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [21. Jun. 2015]:

[Profiler Reports]

> It might not give any useful information. However, the best way to know
> is to look at it.

The first profiler report is after 105 minutes of Emacs uptime.
I had captured infos via org-protocol, refiled them to another
file and then wanted to navigate (arrow keys) to the TODO item in
order to mark it done.  It took seconds till the cursor moved.
Sadly I saved only the memory profiler report.

Then I wrote an reply to your message and while examining the
situation, there was another slow down, when I wanted to switch
buffers via helm, this did nothing for a few secs.  This are the
second reports, only minutes later.

Then I typed ahead and there was a slow down while typing.
System began to swap, emnacs did not respond, I killed Emacs,
firefox, was not able to do a swapoff -a because of memory
restrictions, rebooted the computer, started Emacs with org-mode,
tried to go to the last clocked-in item: and there was a slow
down after say 2 minutes (third profiler reports).

These reports are attachet.

HTH, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

[-- Attachment #2: profiler-report-cpu-2.txt.xz --]
[-- Type: application/x-xz, Size: 6468 bytes --]

[-- Attachment #3: profiler-report-cpu-3.txt.xz --]
[-- Type: application/x-xz, Size: 5476 bytes --]

[-- Attachment #4: profiler-report-mem-3.txt.xz --]
[-- Type: application/x-xz, Size: 15916 bytes --]

[-- Attachment #5: profiler-report.txt.xz --]
[-- Type: application/x-xz, Size: 43536 bytes --]

[-- Attachment #6: profiler-report-mem-2.txt.xz --]
[-- Type: application/x-xz, Size: 10708 bytes --]

  parent reply	other threads:[~2015-06-23 10:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  0:51 Why navigating in Org mode is so slow in overview mode? Q
2015-06-17  2:22 ` Q
2015-06-17  7:51 ` Nicolas Goaziou
2015-06-17 12:12   ` Gregor Zattler
2015-06-17 12:49     ` Andreas Leha
2015-06-17 14:16       ` Gregor Zattler
2015-06-17 14:09     ` Nicolas Goaziou
2015-06-20 20:49       ` Gregor Zattler
2015-06-21  9:13         ` Nicolas Goaziou
2015-06-21  9:46           ` Gregor Zattler
2015-06-23 10:49           ` Gregor Zattler [this message]
2015-06-23 20:15             ` Nicolas Goaziou
2015-07-20  8:39               ` Gregor Zattler
2015-07-20  9:49                 ` Nicolas Goaziou
2015-07-20 12:32                   ` Gregor Zattler
2015-06-22  8:21         ` Sebastien Vauban
2015-06-17 17:13   ` Qiang Fang
2015-06-28 11:43 ` Stefan-W. Hahn

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=20150623104921.GA6709@boo.workgroup \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@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/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).