From: Carsten Dominik <carsten.dominik@gmail.com>
To: e.fraga@ucl.ac.uk
Cc: emacs-orgmode@gnu.org, Rainer Stengele <rainer.stengele@diplan.de>
Subject: Re: org-mode on sloooow computer
Date: Sat, 25 Apr 2009 05:51:48 +0200 [thread overview]
Message-ID: <F5EABAF9-4B13-4E46-A471-1F62125A66E8@gmail.com> (raw)
In-Reply-To: <18930.15516.830598.234897@pinto.chemeng.ucl.ac.uk>
On Apr 25, 2009, at 12:26 AM, Eric S Fraga wrote:
> Carsten Dominik writes:
>> Hmmm, `org-up-heading-all' still gets called, this should no longer
>> happen.
>> I wonder why, when.
>
> There must have been an error in recompilation after pulling the
> updates with git. Although I asked emacs to recompile the directory,
> it must have done something strange. I've cleared out the elc files
> and compiled the whole directory and this is what I get now (which
> indicates yet another improvement!):
>
> org-agenda 1 1.114424
> 1.114424
> org-agenda-list 1 0.889913
> 0.889913
> org-dblock-write:clocktable 7 0.586827
> 0.0838324285
> org-get-clocktable 1 0.427968
> 0.427968
> org-update-dblock 1 0.3902330000
> 0.3902330000
> org-prepare-agenda-buffers 2 0.267907
> 0.1339535
> org-agenda-get-day-entries 6 0.255334
> 0.0425556666
> org-agenda-get-restriction-and-command 1 0.224329
> 0.224329
> org-clock-sum 6 0.195653
> 0.0326088333
> org-agenda-get-scheduled 6 0.145536
> 0.024256
> org-prepare-agenda 1 0.128176
> 0.128176
> org-refresh-category-properties 12 0.0830839999
> 0.0069236666
> org-get-tags-at 8 0.059022
> 0.00737775
> org-up-heading-safe 21 0.0560520000
> 0.0026691428
> org-get-entries-from-diary 1 0.042899
> 0.042899
> ...
>
>> If you want to help:
>>
>> 1. reload uncompiled-code:
>>
>> C-u C-c C-x r
>
> Ummm, this doesn't work for me? C-c C-x r is undefined.
You need to be in an org-mode buffer for this..
>
>> 2. Arm the function
>>
>> M-x debug-on-entry RET org-up-heading-all RET
>>
>> 3. TUrn on debugging on error (needed, but hard to explain here)
>>
>> You can best do this from the "Options" menu, "Enter Debugger on
>> Error"
>>
>> 4. Produce your agenda. You will get a backtrace buffer, which I
>> would like to see...
>
> I don't get a backtrace buffer, which I guess now makes sense since
> org-up-heading-all doesn't seem to get invoked any more.
yes..
>
>> if you want to hunt for more improvements, looking at
>> this table, much can be gained by turning off the
>> clocktable in the agenda and only turning it on
>> interactively with "R" when you really need it.
>
> Yep, this helps as well:
>
> org-agenda 1 0.963539
> 0.963539
> org-agenda-list 1 0.739349
> 0.739349
> org-finalize-agenda-entries 1 0.286326
> 0.286326
> org-agenda-highlight-todo 8 0.282616
> 0.035327
> org-agenda-get-day-entries 6 0.2574450000
> 0.0429075000
> org-agenda-get-restriction-and-command 1 0.224016
> 0.224016
> org-agenda-get-scheduled 6 0.147105
> 0.0245175
> org-prepare-agenda 1 0.1283210000
> 0.1283210000
> org-prepare-agenda-buffers 1 0.1202870000
> 0.1202870000
> org-get-tags-at 8 0.059197
> 0.007399625
> org-up-heading-safe 21 0.056139
> 0.0026732857
> org-get-entries-from-diary 1 0.043058
> 0.043058
> ...
>
> However, I may actually leave the clock display on by default as it
> has a psychological effect that is worthwhile for my working
> practices; but at least I know that turning it off might be worthwhile
> on the Asus.
Of course, this i what I meant.
>
> In any case, I am impressed: from 4.5 seconds to less than a second in
> one day! Can you do the same for my 2+ day optimisation runs I
> require in my research? ;-)
:-) Someone needs to write a profiler for that. In fact, clocking your
work and looking at the biggest time consumers may help :-)
Thanks, this was a fun day.
- Carsten
next prev parent reply other threads:[~2009-04-25 3:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:38 org-mode on sloooow computer Eric S Fraga
2009-04-23 19:15 ` Sven Bretfeld
2009-04-23 20:30 ` Carsten Dominik
2009-04-24 9:22 ` Eric S Fraga
2009-04-24 9:42 ` Carsten Dominik
2009-04-24 9:51 ` Eric S Fraga, Eric S Fraga
2009-04-24 10:25 ` Eric S Fraga
2009-04-24 11:35 ` Carsten Dominik
2009-04-24 12:51 ` Matthew Lundin
2009-04-24 15:27 ` Leo
2009-04-24 15:57 ` Nick Dokos
2009-04-24 16:22 ` Leo
2009-04-25 4:06 ` Samuel Wales
2009-04-23 20:26 ` Carsten Dominik
2009-04-23 22:10 ` Eric S Fraga, Eric S Fraga
2009-04-24 5:03 ` Carsten Dominik
2009-04-24 8:24 ` Eric S Fraga, Eric S Fraga
2009-04-24 9:01 ` Carsten Dominik
2009-04-24 13:37 ` Rainer Stengele
2009-04-24 13:49 ` Carsten Dominik
2009-04-24 15:47 ` Eric S Fraga, Eric S Fraga
2009-04-24 18:25 ` Carsten Dominik
2009-04-24 22:26 ` Eric S Fraga, Eric S Fraga
2009-04-25 3:51 ` Carsten Dominik [this message]
2009-04-25 8:19 ` Eric S Fraga, Eric S Fraga
2009-04-25 16:25 ` Bernt Hansen
2009-04-30 14:13 ` Carsten Dominik
2009-04-24 14:47 ` Carsten Dominik
2009-04-28 10:33 ` Rainer Stengele
2009-04-30 14:14 ` Carsten Dominik
2009-08-31 17:49 ` Daniel Martins
2009-08-31 18:02 ` Leo
2009-08-31 18:12 ` Daniel Martins
2009-08-31 18:41 ` Matt Lundin
2009-08-31 21:03 ` Daniel Martins
2009-08-31 21:11 ` Leo
2009-08-31 21:25 ` Daniel Martins
2009-09-01 4:20 ` Carsten Dominik
2009-09-01 13:15 ` Daniel Martins
2009-09-02 7:15 ` Carsten Dominik
2009-08-31 18:14 ` 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=F5EABAF9-4B13-4E46-A471-1F62125A66E8@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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).