From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Groth Subject: Re: [Orgmode] Slow speed of week and month views Date: Fri, 04 Aug 2017 17:14:26 +0200 Message-ID: <87efsre565.fsf@grothesque.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54375) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddeJ6-0005GI-C2 for emacs-orgmode@gnu.org; Fri, 04 Aug 2017 11:14:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddeJ3-0006qC-EF for emacs-orgmode@gnu.org; Fri, 04 Aug 2017 11:14:32 -0400 Received: from mail6.webfaction.com ([31.170.123.134]:56304 helo=smtp.webfaction.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ddeJ3-0006oH-7R for emacs-orgmode@gnu.org; Fri, 04 Aug 2017 11:14:29 -0400 Received: from localhost (s8s38-1-88-180-226-12.fbx.proxad.net [88.180.226.12]) by smtp.webfaction.com (Postfix) with ESMTPSA id 5AC9C60224D4D for ; Fri, 4 Aug 2017 15:14:26 +0000 (UTC) In-Reply-To: E8146C2B-CF2E-47F8-9015-307D5DFDEEF5@gmail.com 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" To: emacs-orgmode@gnu.org Carsten Dominik wrote in 2010: > I am afraid I don't see any major speed improvements that could > make this happen. Yes, one could parse all the files once, build > a table in memory and get the entries for each day from there - > but that comes down to a complete rewrite of the parser, maybe > even to switching to an internal representation model for > Org-mode. > I don't see that happening, I am afraid. Computing the agenda month view takes 20 seconds in my case. That's perhaps the most serious problem with orgmode as I (and I suppose others as well) use it. It would be great if this issue could be solved after all. Would it be really so difficult to do? The actual parsing seems to be done in the function org-agenda-get-day-entries as called by org-agenda-list. Inside org-agenda-get-day-entries the crucial bit seems to be (org-agenda-today-p date). If that bit got replaced by something that matches more than a single day, wouldn't this mostly do the trick? This is much easier than "rewriting the parser", so it seems that I'm overlooking some problems.