From: Carsten Dominik <carsten.dominik@gmail.com>
To: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org, e.fraga@ucl.ac.uk
Subject: Re: org-mode on sloooow computer
Date: Thu, 30 Apr 2009 16:14:45 +0200 [thread overview]
Message-ID: <91110B32-05B5-4EAA-A845-50B5333302AF@gmail.com> (raw)
In-Reply-To: <49F6DB6B.9040201@diplan.de>
On Apr 28, 2009, at 12:33 PM, Rainer Stengele wrote:
> Carsten Dominik schrieb:
>> I have just pushed one more optimization which may improve things a
>> bit
>> for you, Rainer.
>>
>> - Carsten
>> ...
>
>
> Hi Carsten,
>
> results see here:
>
>
> before your last optimsation:
>
> org-run-agenda-series
> 1 1.797 1.797
>
> after your optimisation (see below):
>
> org-run-agenda-series
> 1 1.703 1.703
> org-agenda
> 1 1.703 1.703
> org-let2
> 2 1.3900000000 0.6950000000
> org-agenda-list
> 1 1.2810000000 1.2810000000
> org-agenda-get-day-entries
> 12 1.202 0.1001666666
> org-agenda-get-scheduled
> 10 0.7969999999 0.0797
> org-end-of-subtree
> 1533 0.4400000000 0.0002870189
> org-time-string-to-absolute
> 1635 0.2360000000 0.0001443425
> org-prepare-agenda
> 3 0.2189999999 0.073
> org-prepare-agenda-buffers
> 1 0.2029999999 0.2029999999
> org-parse-time-string
> 1805 0.188 0.0001041551
> org-agenda-get-timestamps
> 10 0.14 0.0140000000
> org-todo-list
> 1 0.109 0.109
> org-agenda-get-deadlines
> 10 0.094 0.0094
> org-closest-date
> 240 0.094 0.0003916666
> org-back-to-heading
> 2206 0.094 4.26...e-005
> org-finalize-agenda
> 3 0.094 0.0313333333
> org-let
> 1 0.094 0.094
> org-outline-level
> 1533 0.094 6.13...e-005
> org-agenda-get-todos
> 2 0.093 0.0465
> org-date-to-gregorian
> 480 0.078 0.0001625
> org-agenda-fontify-priorities
> 1 0.078 0.078
> org-get-entries-from-diary
> 5 0.063 0.0126
> org-agenda-skip
> 3220 0.063 1.95...e-005
> org-agenda-skip-if
> 167 0.063 0.0003772455
> org-agenda-skip-entry-if
> 167 0.063 0.0003772455
> org-refresh-category-properties
> 2 0.0470000000 0.0235000000
> org-get-todo-state
> 335 0.047 0.0001402985
> org-agenda-get-blocks
> 10 0.046 0.0046
> org-agenda-files
> 4 0.032 0.008
> org-get-effort
> 72 0.031 0.0004305555
> org-entry-get
> 72 0.031 0.0004305555
> org-format-agenda-item
> 74 0.031 0.0004189189
> org-at-date-range-p
> 219 0.031 0.0001415525
> org-get-wdays
> 150 0.016 0.0001066666
> org-entries-lessp
> 219 0.016 7.30...e-005
> org-agenda-get-sexps
> 10 0.016 0.0016
> org-agenda-align-tags
> 1 0.016 0.016
> org-finalize-agenda-entries
> 5 0.016 0.0032
> org-check-agenda-file
> 14 0.015 0.0010714285
> org-get-property-block
> 72 0.015 0.0002083333
>
>
>
> So it looks like I have come from 1.797 down to 1.703.
> And by the way - the times are even now varying between
> org-run-agenda-series
> 1 1.563 1.563
> and little over 2 seconds.
>
>
> Will I see much improvement when archiving a lot of subtrees inside
> the org file?
I don't think so, archiving to a separate file is the best way to keep
things fast.
- Carsten
>
>
> Thanks so much for this special "Rainer" optimisation ;)
> I also dream of always carrying around a small netbook running
> mainly emacs with org-mode ...
>
>
> Rainer
>
>
>> On Apr 24, 2009, at 3:37 PM, Rainer Stengele wrote:
>>
>>> Hi Carsten,
>>>
>>> strange enough the latest git version does not improve time for my
>>> agenda at all.
>>> It still is as slow or fast - however you see it.
>>>
>>> org-version is 6.26trans
>>>
>>> ,----
>>> | org-run-agenda-series
>>> 1 1.797 1.797
>>> | org-agenda
>>> 1 1.797 1.797
>>> | org-let2
>>> 2 1.422 0.711
>>> | org-agenda-get-day-entries
>>> 12 1.248 0.104
>>> | org-agenda-list
>>> 1 1.2349999999 1.2349999999
>>> | org-agenda-get-scheduled
>>> 10 0.7979999999 0.0798
>>> | org-end-of-subtree
>>> 1533 0.6430000000 0.0004194390
>>> | org-prepare-agenda
>>> 3 0.359 0.1196666666
>>> | org-prepare-agenda-buffers
>>> 1 0.25 0.25
>>> | org-back-to-heading
>>> 2198 0.1880000000 8.55...e-005
>>> | org-todo-list
>>> 1 0.187 0.187
>>> | org-agenda-get-todos
>>> 2 0.171 0.0855
>>> | org-refresh-category-properties
>>> 2 0.141 0.0705
>>> | org-get-entries-from-diary
>>> 5 0.126 0.0252
>>> | org-agenda-get-deadlines
>>> 10 0.107 0.0107
>>> | org-agenda-get-timestamps
>>> 10 0.078 0.0078
>>> | org-outline-level
>>> 5376 0.064 1.19...e-005
>>> | org-agenda-skip-if
>>> 167 0.061 0.0003652694
>>> | org-agenda-skip-entry-if
>>> 167 0.061 0.0003652694
>>> | org-agenda-get-blocks
>>> 10 0.046 0.0046
>>> | org-check-agenda-file
>>> 14 0.032 0.0022857142
>>> | org-get-todo-state
>>> 333 0.031 9.30...e-005
>>> | org-finalize-agenda
>>> 3 0.016 0.0053333333
>>> | org-time-string-to-absolute
>>> 1627 0.016 9.83...e-006
>>> | org-agenda-get-sexps
>>> 10 0.016 0.0016
>>> | org-at-date-range-p
>>> 217 0.016 7.37...e-005
>>> | org-agenda-align-tags
>>> 1 0.016 0.016
>>> | org-let
>>> 1 0.016 0.016
>>> | org-agenda-files
>>> 4 0.015 0.00375
>>> | org-agenda-skip
>>> 3213 0.015 4.66...e-006
>>> | org-on-heading-p
>>> 164 0.015 9.14...e-005
>>> | org-agenda-set-mode-name
>>> 1 0.0 0.0
>>> | org-date-to-gregorian
>>> 474 0.0 0.0
>>> | org-delete-overlay
>>> 65 0.0 0.0
>>> | org-agenda-reset-markers
>>> 1 0.0 0.0
>>> | org-find-base-buffer-visiting
>>> 14 0.0 0.0
>>> | org-set-sorting-strategy
>>> 2 0.0 0.0
>>> | org-get-effort
>>> 69 0.0 0.0
>>> | org-downcase-keep-props
>>> 41 0.0 0.0
>>> | org-get-agenda-file-buffer
>>> 14 0.0 0.0
>>> | org-fit-agenda-window
>>> 1 0.0 0.0
>>> | org-agenda-check-for-timestamp-as-reason-to-ignore-todo-item
>>> 189 0.0 0.0
>>> | org-entry-get
>>> 69 0.0 0.0
>>> | org-agenda-post-command-hook
>>> 2 0.0 0.0
>>> | org-overlay-get
>>> 241 0.0 0.0
>>> | org-agenda-cleanup-fancy-diary
>>> 5 0.0 0.0
>>> | org-get-wdays
>>> 150 0.0 0.0
>>> | org-parse-time-string
>>> 1797 0.0 0.0
>>> | org-entries-lessp
>>> 215 0.0 0.0
>>> | org-trim
>>> 29 0.0 0.0
>>> | org-closest-date
>>> 237 0.0 0.0
>>> | org-agenda-add-inherited-tags
>>> 72 0.0 0.0
>>> | org-modify-diary-entry-string
>>> 5 0.0 0.0
>>> | org-make-overlay
>>> 65 0.0 0.0
>>> | org-file-menu-entry
>>> 2 0.0 0.0
>>> | org-add-to-diary-list
>>> 5 0.0 0.0
>>> | org-split-string
>>> 39 0.0 0.0
>>> | org-activate-bracket-links
>>> 1 0.0 0.0
>>> | org-add-props
>>> 186 0.0 0.0
>>> | org-agenda-add-time-grid-maybe
>>> 3 0.0 0.0
>>> | org-get-category
>>> 69 0.0 0.0
>>> | org-days-to-iso-week
>>> 3 0.0 0.0
>>> | org-agenda-mode
>>> 1 0.0 0.0
>>> | org-uniquify
>>> 4 0.0 0.0
>>> | org-agenda-new-marker
>>> 107 0.0 0.0
>>> | org-agenda-todayp
>>> 20 0.0 0.0
>>> | org-format-agenda-item
>>> 72 0.0 0.0
>>> | org-overlays-in
>>> 1 0.0 0.0
>>> | org-get-property-block
>>> 69 0.0 0.0
>>> | org-fontify-priorities
>>> 1 0.0 0.0
>>> | org-get-tags-at
>>> 69 0.0 0.0
>>> | org-overlay-put
>>> 130 0.0 0.0
>>> | org-get-todo-face
>>> 68 0.0 0.0
>>> | org-compile-prefix-format
>>> 2 0.0 0.0
>>> | org-agenda-highlight-todo
>>> 72 0.0 0.0
>>> | org-agenda-ndays-to-span
>>> 1 0.0 0.0
>>> | org-agenda-deadline-face
>>> 4 0.0 0.0
>>> | org-add-hook
>>> 2 0.0 0.0
>>> | org-time-string-to-time
>>> 170 0.0 0.0
>>> | org-agenda-fontify-priorities
>>> 1 0.0 0.0
>>> | org-agenda-format-date-aligned
>>> 3 0.0 0.0
>>> | org-diary-default-entry
>>> 5 0.0 0.0
>>> | org-font-lock-add-tag-faces
>>> 1 0.0 0.0
>>> | org-get-priority
>>> 69 0.0 0.0
>>> | org-remove-uniherited-tags
>>> 69 0.0 0.0
>>> | org-get-time-of-day
>>> 37 0.0 0.0
>>> | org-finalize-agenda-entries
>>> 4 0.0 0.0
>>> | org-unhighlight
>>> 2 0.0 0.0
>>> | org-before-change-function
>>> 199 0.0 0.0
>>> `----
>>>
>>> my org file is about 15000 lines large.
>>>
>>>
>>> Rainer
>>>
>>>
>>> Carsten Dominik schrieb:
>>>>
>>>> On Apr 24, 2009, at 10:24 AM, Eric S Fraga wrote:
>>>>
>>>>> Carsten Dominik writes:
>>>>>> On Apr 24, 2009, at 12:10 AM, Eric S Fraga wrote:
>>>>>>> Which part can you not reproduce?
>>>>>>
>>>>>> When I have the agenda on an arbitrary date, pressing "j" does
>>>>>> *not*
>>>>>> first switch the agenda to today.
>>>>>
>>>>> <blush>
>>>>>
>>>>> Okay, the problem was mine: I had included a very useful method,
>>>>> originally from Tassilo (cf. th-calendar-open-agenda), which would
>>>>> have the agenda view updated when the calendar view changed.
>>>>> Removing
>>>>> this gives the behaviour I was now looking for, and which is
>>>>> indeed
>>>>> the default behaviour. Apologies for the noise.
>>>>>
>>>>> </blush>
>>>>>
>>>>> Actually, this experience is a testament to the insidious nature
>>>>> (in a
>>>>> positive way) of org-mode: it is taking over my life! I used to
>>>>> have
>>>>> the Emacs diary + calendar as the focus of my attention for task
>>>>> and
>>>>> time management and org-mode was initially an addition to this.
>>>>> org-mode is now almost completely the focus and I really need to
>>>>> clean
>>>>> up my customisations to remove the old vestiges of how I used to
>>>>> work.
>>>>>
>>>>> Again, apologies and continued thanks for an excellent system
>>>>> which I
>>>>> could no longer live without!
>>>>
>>>> I still would like to to see profiling information as I described
>>>> in my
>>>> message from yesterday, so see if specific operations are
>>>> particularly
>>>> slow on netbooks or a zaurus.
>>>>
>>>> - Carsten
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Remember: use `Reply All' to send replies to the list.
>>>> Emacs-orgmode@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
next prev parent reply other threads:[~2009-05-03 16:14 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
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 [this message]
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=91110B32-05B5-4EAA-A845-50B5333302AF@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).