From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Performance problem
Date: Mon, 23 May 2011 19:20:51 +0200 [thread overview]
Message-ID: <jkhqa8xk4v.ln2@news.c0t0d0s0.de> (raw)
In-Reply-To: en0qa8x77i.ln2@news.c0t0d0s0.de
Hi,
Michael Welle <mwe012008@gmx.net> writes:
[...]
>>> I don't blame org-mode for that behaviour, but maybe someone of you has
>>> observed such behaviour, too? Any hints on debugging?
>>
>> M-x elp-instrument-package org [RET]
>> M-x org-agenda-list
>> M-x elp-results
> Ah, nice. Now I have to wait til the misbehaviour occurs again.
a different machine, but the same problem ;). This is a 'bad' run
org-agenda-list 1 17.646198 17.646198
org-agenda-get-day-entries 868 12.302421999 0.0141732972
org-agenda-get-sexps 868 11.237522999 0.0129464550
org-prepare-agenda-buffers 2 4.5861040000 2.2930520000
org-prepare-agenda 1 4.524422 4.524422
org-get-agenda-file-buffer 1116 4.2117990000 0.0037740134
org-mode 124 1.5946210000 0.0128598467
org-install-agenda-files-menu 124 1.0290419999 0.0082987258
org-agenda-files 134 0.84026 0.0062705970
org-find-base-buffer-visiting 1116 0.6872910000 0.0006158521
org-get-entries-from-diary 7 0.4210619999 0.0601517142
org-agenda-get-blocks 868 0.3384840000 0.0003899585
And this is a 'good' run
org-agenda-list 1 3.935774 3.935774
org-prepare-agenda-buffers 2 2.894058 1.447029
org-prepare-agenda 1 2.833592 2.833592
org-get-agenda-file-buffer 1116 2.5790829999 0.0023110062
org-mode 124 1.1269950000 0.0090886693
org-install-agenda-files-menu 124 0.8238960000 0.0066443225
org-agenda-files 134 0.6465149999 0.0048247388
org-agenda-get-day-entries 868 0.5411369999 0.0006234297
org-get-entries-from-diary 7 0.49768 0.0710971428
org-find-base-buffer-visiting 1116 0.3149529999 0.0002822159
org-set-startup-visibility 124 0.1660580000 0.0013391774
org-refresh-category-properties 248 0.1442590000 0.0005816895
Looks like it spent most of the extra time in org-agenda-get-day-entries
and org-agenda-get-sexps. Time to have a look at the source code ;).
Regards
hmw
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Flood - Your friendly network packet generator
http://www.c0t0d0s0.de/flood/flood.html
next prev parent reply other threads:[~2011-05-23 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 7:30 Performance problem Michael Welle
2011-05-23 11:50 ` Matt Lundin
2011-05-23 12:32 ` Michael Welle
2011-05-23 17:20 ` Michael Welle [this message]
2011-05-23 18:33 ` Eric S Fraga
2011-05-23 19:26 ` Michael Welle
2011-05-24 12:47 ` Matt Lundin
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=jkhqa8xk4v.ln2@news.c0t0d0s0.de \
--to=mwe012008@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).