unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Justus Winter <4winter@informatik.uni-hamburg.de>
To: Daniel Schoepe <daniel@schoepe.org>,
	Philippe LeCavalier <support@plecavalier.com>,
	notmuch@notmuchmail.org
Subject: Re: nomuch_addresses.py
Date: Tue, 21 Feb 2012 09:15:09 -0000
Date: Tue, 21 Feb 2012 10:15:09 +0100	[thread overview]
Message-ID: <20120221091509.8534.59492@thinkbox.jade-hamburg.de> (raw)
In-Reply-To: <87fweamenf.fsf@schoepe.localhost>

Quoting Daniel Schoepe (2012-02-17 02:28:52) [emphasis mine]:
>Just for completeness: I'm using the nice nottoomuch-addresses.pl script
>[1] by Tomi Ollila *which doesn't require any bindings* and is incredibly
>fast (after generating an initial address database).

I don't get it. The perl script isn't using any library bindings,
mainly because there are no libnotmuch bindings for perl. *But* it
does call the notmuch binary which is worse:

* incredibly high overhead (fork&exec) compared to a simple function
  call (plus maybe some kind of ffi)
* manual and error prone serialization of ''function arguments''
* manual and error prone deserialization of ''return values''
* very limited error reporting and handling capabilities
* any kind of resource (think handle to a xapian database) is lost if
  the process exists resulting in further overhead if the binary is
  called multiple times

I do get the feeling that it is perceived as desirable not to require
any kind of notmuch bindings (David once said something similar about
nmbug).

If that's the case I'd love to hear why and if there's anything we can
do about it.

Justus

  parent reply	other threads:[~2012-02-21  9:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 19:12 nomuch_addresses.py Philippe LeCavalier
2012-02-16 19:46 ` nomuch_addresses.py Jesse Rosenthal
2012-02-16 19:51   ` nomuch_addresses.py Philippe LeCavalier
2012-02-16 20:00     ` nomuch_addresses.py Jesse Rosenthal
2012-02-16 20:03     ` nomuch_addresses.py Daniel Kahn Gillmor
2012-02-17  1:28 ` nomuch_addresses.py Daniel Schoepe
2012-02-17 18:58   ` nomuch_addresses.py Tomi Ollila
2012-02-17 20:33     ` nomuch_addresses.py Sebastian Spaeth
2012-02-17 20:46       ` nomuch_addresses.py Tomi Ollila
2012-02-18  3:04         ` nomuch_addresses.py Philippe LeCavalier
2012-02-18  5:15           ` nomuch_addresses.py Tomi Ollila
2012-02-21  1:25   ` nomuch_addresses.py Philippe LeCavalier
2012-02-21  9:15   ` Justus Winter [this message]
2012-02-21 11:23     ` nomuch_addresses.py Tomi Ollila
2012-02-21 13:53     ` nomuch_addresses.py Daniel Schoepe
2012-02-21 16:33       ` nomuch_addresses.py Jesse Rosenthal
2012-02-22 13:07         ` nomuch_addresses.py Jani Nikula
2012-02-21 20:30     ` nomuch_addresses.py David Bremner

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120221091509.8534.59492@thinkbox.jade-hamburg.de \
    --to=4winter@informatik.uni-hamburg.de \
    --cc=daniel@schoepe.org \
    --cc=notmuch@notmuchmail.org \
    --cc=support@plecavalier.com \
    /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://yhetil.org/notmuch.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).