From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Speeding up the agenda search Date: Wed, 24 Oct 2012 16:12:49 +0200 Message-ID: <87bofs2c2m.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TR1hK-00007j-Gz for emacs-orgmode@gnu.org; Wed, 24 Oct 2012 10:12:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TR1hB-0007tT-09 for emacs-orgmode@gnu.org; Wed, 24 Oct 2012 10:12:42 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:55466) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TR1hA-0007tJ-QA for emacs-orgmode@gnu.org; Wed, 24 Oct 2012 10:12:32 -0400 Received: by mail-wi0-f177.google.com with SMTP id hj13so405642wib.12 for ; Wed, 24 Oct 2012 07:12:32 -0700 (PDT) In-Reply-To: (Marcelo de Moraes Serpa's message of "Sat, 20 Oct 2012 00:29:58 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcelo de Moraes Serpa Cc: Org Mode Hi Marcelo, Marcelo de Moraes Serpa 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