From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wes Hardaker Subject: Re: OBBDB(3) or org-contacts Date: Tue, 08 Jan 2013 09:16:41 -0800 Message-ID: <0lobgzh9xi.fsf@wjh.hardakers.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TscnH-00083k-BS for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 12:16:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TscnD-0000hq-GI for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 12:16:55 -0500 Received: from mail.hardakers.net ([168.150.236.43]:52896) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TscnD-0000h2-67 for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 12:16:51 -0500 In-Reply-To: (gour@atmarama.net's message of "Mon, 7 Jan 2013 21:03:24 +0100") 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: Gour Cc: emacs-orgmode@gnu.org Gour writes: > Based on this description it seems that org-contacts is more suitable > for the task than BBDB(3) offering ability to have custom format, easy > editing of contacts etc., but I do wonder about scalability considering > the following post > (http://www.hardakers.net/code/bbdb-to-org-contacts/) where the author > of bbdb-to-org-contacts converter wrote: "Once I point org-contacts at > my newly generated file containing 831 records it make org-contacts > really really slow down. I wouldn't care about the normal record > searching process for just looking something up, but it makes loading a > message in gnus unusable (5 second delay per message)." FYI, I tried (again) to use org-contacts a while back and still see the same speed problems. It's great for small contacts, but not for large. I think what would be needed would be to read the file and store it in an elisp structure and then just stat() the file every time a lookup happened and if it hasn't changed, then use the elisp or else reparse. It's not like the data should be changing *that* much so it shouldn't need to be reread a lot. And it's the parsing/searching that takes too long. But I certainly like the org-mode format much much much better than bbdb(3). Which I'm still using, unfortunately. -- Wes Hardaker My Pictures: http://capturedonearth.com/ My Thoughts: http://pontifications.hardakers.net/