From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: RFC: output json from notmuch?
Date: Sun, 13 Dec 2009 19:26:02 -0400 [thread overview]
Message-ID: <87hbrupib9.fsf@pivot.cs.unb.ca> (raw)
In-Reply-To: <87iqcapijl.fsf@pivot.cs.unb.ca>
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
On Sun, 13 Dec 2009 19:21:02 -0400, David Bremner <david@tethera.net> wrote:
>
> Attachments: json output of a message from carl, and the equivalent
> sexpr as parsed by json.el.
>
uh, right. Second time lucky.
[-- Attachment #2: json encoded message --]
[-- Type: application/octet-stream, Size: 2283 bytes --]
{
"match": true,
"header": {
"Cc": "",
"Subject": "Re: [notmuch] Patch for xapian defect #250",
"From": "Carl Worth <cworth@cworth.org>",
"summary": "Carl Worth <cworth@cworth.org> (Fri. 01:13) ()",
"To": "Kan-Ru Chen <kanru@kanru.info>, notmuch <notmuch@notmuchmail.org>",
"Bcc": "",
"Date": "Thu, 10 Dec 2009 21:13:07 -0800"
},
"id": "87638e3xgc.fsf@yoom.home.cworth.org",
"filename": "/home/bremner/Maildir/.list.notmuch/new/1260508402.30807.pivot.cs.unb.ca",
"depth": 1,
"parts": [
{
"content-type": "text/plain",
"id": 3,
"text": "On Thu, 10 Dec 2009 15:00:42 +0800, Kan-Ru Chen <kanru@kanru.info> wrote:\n> The termlist is already sorted, so this is the patch trying to minimize\n> the modification of database as suggested in the comment and Carl's\n> TODO file.\n\nFantastic, Kan-Ru!\n\n> My poor profiling shows not much, but some improvement.\n\nNow you're just understating for sake of the pun. A 5-6x performance\nimprovement looks great. And I see that as well in my testing:\n\nBefore:\n\n\t$ time notmuch tag +foo tag:sent\n\treal 3m18.067s\n\t$ time notmuch tag -foo tag:sent\n\treal 3m12.940s\n\nAfter:\n\n\t$ time notmuch tag +foo tag:sent\n real 0m31.497s\n\t$ time notmuch tag -foo tag:sent\n\treal 0m28.722s\n\nI didn't flush the OS caches between runs, but a subsequent run of the\n\"before\" code still performed similarly slow:\n\n\t$ time notmuch tag +foo tag:sent\n\treal 3m7.172s\n\nAnd if I *had* used cold caches for every run the benefit of the patch\nwould have looked even better.\n\nAnyway, we should get this upstream to the Xapian folks straight\naway. I expect they'll want to see a patch to the chert backend as well\nas the flint backend, (but fortunately the relevant code looks very\nsimilar if not identical).\n\nThanks again,\n\n-Carl\n"
},
{
"content-type": "application/pgp-signature",
"id": 4
},
{
"content-type": "text/plain",
"id": 5,
"text": "_______________________________________________\nnotmuch mailing list\nnotmuch@notmuchmail.org\nhttp://notmuchmail.org/mailman/listinfo/notmuch\n"
}
]
}
[-- Attachment #3: msg converted to sexpr by json.el --]
[-- Type: application/octet-stream, Size: 2065 bytes --]
((parts .
[((text . "On Thu, 10 Dec 2009 15:00:42 +0800, Kan-Ru Chen <kanru@kanru.info> wrote:\n> The termlist is already sorted, so this is the patch trying to minimize\n> the modification of database as suggested in the comment and Carl's\n> TODO file.\n\nFantastic, Kan-Ru!\n\n> My poor profiling shows not much, but some improvement.\n\nNow you're just understating for sake of the pun. A 5-6x performance\nimprovement looks great. And I see that as well in my testing:\n\nBefore:\n\n $ time notmuch tag +foo tag:sent\n real 3m18.067s\n $ time notmuch tag -foo tag:sent\n real 3m12.940s\n\nAfter:\n\n $ time notmuch tag +foo tag:sent\n real 0m31.497s\n $ time notmuch tag -foo tag:sent\n real 0m28.722s\n\nI didn't flush the OS caches between runs, but a subsequent run of the\n\"before\" code still performed similarly slow:\n\n $ time notmuch tag +foo tag:sent\n real 3m7.172s\n\nAnd if I *had* used cold caches for every run the benefit of the patch\nwould have looked even better.\n\nAnyway, we should get this upstream to the Xapian folks straight\naway. I expect they'll want to see a patch to the chert backend as well\nas the flint backend, (but fortunately the relevant code looks very\nsimilar if not identical).\n\nThanks again,\n\n-Carl\n")
(id . 3)
(content-type . "text/plain"))
((id . 4)
(content-type . "application/pgp-signature"))
((text . "_______________________________________________\nnotmuch mailing list\nnotmuch@notmuchmail.org\nhttp://notmuchmail.org/mailman/listinfo/notmuch\n")
(id . 5)
(content-type . "text/plain"))])
(depth . 1)
(filename . "/home/bremner/Maildir/.list.notmuch/new/1260508402.30807.pivot.cs.unb.ca")
(id . "87638e3xgc.fsf@yoom.home.cworth.org")
(header
(Date . "Thu, 10 Dec 2009 21:13:07 -0800")
(Bcc . "")
(To . "Kan-Ru Chen <kanru@kanru.info>, notmuch <notmuch@notmuchmail.org>")
(summary . "Carl Worth <cworth@cworth.org> (Fri. 01:13) ()")
(From . "Carl Worth <cworth@cworth.org>")
(Subject . "Re: [notmuch] Patch for xapian defect #250")
(Cc . ""))
(match . t))
[-- Attachment #4: Type: text/plain, Size: 255 bytes --]
--
David Bremner Professor, UNB Computer Science
bremner@unb.ca
http://www.cs.unb.ca/~bremner Cross Appointment, UNB Mathematics
http://www.mitacs.ca/ MITACS Atlantic Scientific Director
next prev parent reply other threads:[~2009-12-13 23:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 23:21 RFC: output json from notmuch? David Bremner
2009-12-13 23:26 ` David Bremner [this message]
2009-12-14 0:05 ` Scott Robinson
2009-12-14 0:42 ` David Bremner
2009-12-14 22:41 ` Carl Worth
2009-12-14 22:34 ` Carl Worth
2009-12-14 0:07 ` Marten Veldthuis
2009-12-14 22:30 ` Carl Worth
2009-12-14 23:10 ` David Bremner
2009-12-18 5:33 ` [PATCH] JSON output for notmuch-search and notmuch-show Scott Robinson
2009-12-18 12:59 ` [PATCH] Add an "--output=(json|text|)" command-line option to both " david
2009-12-18 17:33 ` Carl Worth
2009-12-18 18:45 ` Scott Robinson
2009-12-19 0:36 ` David Bremner
2009-12-23 5:58 ` Carl Worth
2009-12-19 14:55 ` Prototype of --show option to control what is shown david
2009-12-19 14:55 ` [PATCH 1/3] rename option to select output format to --format from --output david
2009-12-19 14:55 ` [PATCH 2/3] notmuch-show.c: make calls to format functions conditional david
2009-12-19 14:55 ` [PATCH 3/3] notmuch-show.c: prototype tabular output format, with output control david
2010-03-09 19:51 ` Carl Worth
2010-03-09 20:19 ` David Bremner
2010-03-10 9:25 ` Carl Worth
2010-03-10 15:34 ` David Bremner
2009-12-20 20:31 ` [PATCH] notmuch-query.el: new file to support access to the notmuch database david
2009-12-21 17:21 ` Carl Worth
2009-12-21 18:01 ` David Bremner
2010-02-24 12:52 ` [PATCH v2] " david
2010-04-05 16:46 ` [PATCH v3] " david
2010-04-05 16:59 ` David Edmondson
2010-04-05 18:13 ` Carl Worth
2010-02-23 19:56 ` [PATCH] Add an "--output=(json|text|)" command-line option to both notmuch-search and notmuch-show Carl Worth
2010-02-23 21:00 ` JSON output as default [was: Re: [PATCH] Add an "--output=(json|text|)" command-line option...] Jameson Rollins
2010-02-23 23:35 ` Carl Worth
2010-02-24 13:54 ` Sebastian Spaeth
2009-12-18 17:31 ` [PATCH] JSON output for notmuch-search and notmuch-show Carl Worth
2009-12-18 18:47 ` Scott Robinson
2009-12-23 5:48 ` Carl Worth
2009-12-31 8:54 ` Scott Robinson
2009-12-31 12:49 ` David Bremner
2009-12-25 12:53 ` 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=87hbrupib9.fsf@pivot.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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).