From: Carsten Dominik <email@example.com> To: Jason Jackson <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [PERF] Slow Org Agenda Custom Commands Date: Sun, 18 Jan 2009 20:50:18 +0100 [thread overview] Message-ID: <5804861A-7F2F-4034-B4D0-19910F6A1984@uva.nl> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1.1: Type: text/plain, Size: 3027 bytes --] On Jan 12, 2009, at 6:56 AM, Jason Jackson wrote: > Thank you Matthew, this improved the performance to an acceptable > ~half second > > I still wonder if multiple property searches could be optimized > somehow, but for my purposes I'm satisfied =) Hi Jason, property searches are really un-optimized in Org. Tag searches are faster, but also not well optimized. I do have ideas how to improve the situation with some cacheing. However, this is a case where the fact that Org-mode is using plain text files is biting you. It is very hard, between two searched (the first one creating the cache, the second one using it), to be sure that the text base has not been modified by hand. I could probably create a cache and make the user responsible to update it, but I have not made this step. - Carsten > > > For example, you can't use agenda filter commands with org-stuck- > project-list, thus you'd have to resort to a slow property search. > Some people might want to search for high priority stuck projects. > (I solved this by introducing different 'priority' todo states) > > -Jason > > On Mon, Jan 12, 2009 at 1:34 PM, Matthew Lundin <email@example.com> > wrote: > > Hi Jason, > > "Jason Jackson" <firstname.lastname@example.org> writes: > > > I'm using the following org agenda custom command, with a > relatively small > > org-mode text file, and agenda creation is taking around 3-4 > seconds, it > > becomes unbearably worse if I modify stuck-projects to also use > properties > > searches) > > > > Is there anything I can change to speed up the commands execution; > or > > developer changes to org-mode? > > > > (setq org-agenda-custom-commands > > '(("h" "Next Action" > > ( > > (agenda "" > > ((org-agenda-ndays 1) > > (org-agenda-time-grid '()) > > (org-deadline-warning-days 5) > > (org-agenda-sorting-strategy '(time-up priority- > down)) > > (org-agenda-skip-deadline-if-done t) > > (org-agenda-overriding-header "Today's Agenda: ") > > )) > > ;;;;;;; SLOW COMMAND #1 > > (tags "@HOME-habit-__IGNORE-SCHEDULED>\"<2000-01-01>\"/ > TODO|BLOCKED| > > SUBMIT" > > ((org-agenda-sorting-strategy '(priority-down)) > > (org-agenda-overriding-header "Unscheduled Todo > > (@Home): ") > > )) > > As you suggest, any searches for properties other than TODO, LEVEL, > and CATEGORY can be quite slow. > > Have you considered using a todo search and then using secondary > filtering to limit by tag. This would enable you to use either of the > following variables: > > - org-agenda-todo-ignore-with-date > - org-agenda-todo-ignore-scheduled > > Best, > Matt > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacsemail@example.com > http://lists.gnu.org/mailman/listinfo/emacs-orgmode [-- Attachment #1.2: Type: text/html, Size: 4607 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacsfirstname.lastname@example.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2009-01-18 19:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-11 0:08 Jason Jackson 2009-01-12 2:34 ` Matthew Lundin 2009-01-12 5:56 ` Jason Jackson 2009-01-18 19:50 ` Carsten Dominik [this message]
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=5804861A-7F2F-4034-B4D0-19910F6A1984@uva.nl \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PERF] Slow Org Agenda Custom Commands' \ /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
Code repositories for project(s) associated with this 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).