From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Slow speed of week and month views Date: Sun, 06 Aug 2017 00:33:25 +0200 Message-ID: <87lgmxhcga.fsf@nicolasgoaziou.fr> References: <87efsre565.fsf@grothesque.org> <878tiyr9tg.fsf@alphapapa.net> <2017-08-05T23-06-00@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55019) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1de7dS-00025z-1k for emacs-orgmode@gnu.org; Sat, 05 Aug 2017 18:33:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1de7dQ-0001WM-Tb for emacs-orgmode@gnu.org; Sat, 05 Aug 2017 18:33:30 -0400 Received: from relay2-d.mail.gandi.net ([2001:4b98:c:538::194]:48183) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1de7dQ-0001V3-Nd for emacs-orgmode@gnu.org; Sat, 05 Aug 2017 18:33:28 -0400 In-Reply-To: (John Kitchin's message of "Sat, 5 Aug 2017 18:17:09 -0400") 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: John Kitchin Cc: Karl Voit , "emacs-orgmode@gnu.org" Hello, John Kitchin writes: > I can think of two possibilities for a future approach (besides a deep dive > on profiling the current elisp to improve the speed there). They both > involve some substantial coding though, and would probably add > dependencies. I am curious what anyone things about these, or if there are > other ideas. These are interesting ideas, but I'd rather have a deep dive on profiling the current Elisp. > The main point of the database was to get a query language, persistence and > good performance. I have also used caches to speed up using bibtex files, > and my org-contacts with reasonable performance. These have been all elisp, > with no additional dependencies. Maybe one could do something similar to > keep an agenda cache that is persistent and updated via hook > functions. If an agenda cache is required, it can be very simple. Associate entries to agenda files. Whenever a file is modified, drop all the entries. No need to refresh it IMO. I doubt many agenda files are modified between two agenda calls. Regards, -- Nicolas Goaziou