emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Speeding up the agenda search
Date: Wed, 24 Oct 2012 16:12:49 +0200	[thread overview]
Message-ID: <87bofs2c2m.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CACHMzOHPoFJn5cW83B=zbicr+CHp9FFmL089oSsoOz0pN8afYA@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Sat, 20 Oct 2012 00:29:58 -0500")

Hi Marcelo,

Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:

> My list of files in the agenda got to a considerable size. It still
> searchable, but some types of search, such as PROPERTY, usually lock
> down emacs and I'm forced to kill the process. Is there any way to
> speed it up? Perhaps by compiling the elisp files to bytecode? 

Speed of the agenda generation is a often a problem.

It's a delicate one because subjective and objective problems
are often closely entangled in this area (speed of your machine,
perceived acceptable speed for generating the agenda, complexity
of the query, size of your agenda files, etc.)

The only way we can make progress here is by rolling our sleeves
and performing tiny optimizations, one after another.

As a first step, you can try to make a diagnosis the problem by
instrumenting the agenda functions:

  M-x elp-instrument-package RET org-agenda RET

Then doing your agenda query then reporting results 

  M-x elp-results RET

We'll get a rough idea of the time spent and be able to compare
it with the one on other machines.  

Thanks,

-- 
 Bastien

      parent reply	other threads:[~2012-10-24 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  5:29 Speeding up the agenda search Marcelo de Moraes Serpa
2012-10-22 16:36 ` Marcelo de Moraes Serpa
2012-10-22 17:33   ` François Allisson
2012-10-24 14:12 ` Bastien [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=87bofs2c2m.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=celoserpa@gmail.com \
    --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).