From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/7] v2: swap in new IPC package
Date: Sun, 3 Jan 2021 02:06:10 +0000 [thread overview]
Message-ID: <20210103020617.15719-1-e@80x24.org> (raw)
SearchIdxShard was too big and adding the new extindex
stuff made things worse. Since I intend to use IPC
in more places, I figured it'd be good to prove it with
works well by dropping it into the old v2 mix.
The below diffstat is nice
Eric Wong (7):
ipc: some documentation comments
searchidxshard: use PublicInbox::IPC to kill lots of code
searchidxshard: IPC conversion, part 2
searchidxshard: replace index_raw with index_eml
use Eml (or MIME) objects for all indexing paths
ipc: switch to one-way pipes
searchidxshard: use add_xapian directly for v2
lib/PublicInbox/ExtSearchIdx.pm | 38 +++--
lib/PublicInbox/IPC.pm | 127 +++++++++------
lib/PublicInbox/Import.pm | 4 +-
lib/PublicInbox/LeiStore.pm | 18 +--
lib/PublicInbox/SearchIdx.pm | 35 +---
lib/PublicInbox/SearchIdxShard.pm | 257 +++++-------------------------
lib/PublicInbox/Smsg.pm | 13 ++
lib/PublicInbox/V2Writable.pm | 102 +++++-------
t/import.t | 12 +-
t/search.t | 2 +-
10 files changed, 206 insertions(+), 402 deletions(-)
next reply other threads:[~2021-01-03 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 2:06 Eric Wong [this message]
2021-01-03 2:06 ` [PATCH 1/7] ipc: some documentation comments Eric Wong
2021-01-03 2:06 ` [PATCH 2/7] searchidxshard: use PublicInbox::IPC to kill lots of code Eric Wong
2021-01-03 2:06 ` [PATCH 3/7] searchidxshard: IPC conversion, part 2 Eric Wong
2021-01-03 2:06 ` [PATCH 4/7] searchidxshard: replace index_raw with index_eml Eric Wong
2021-01-03 2:06 ` [PATCH 5/7] use Eml (or MIME) objects for all indexing paths Eric Wong
2021-01-03 2:06 ` [PATCH 6/7] ipc: switch to one-way pipes Eric Wong
2021-01-03 2:06 ` [PATCH 7/7] searchidxshard: use add_xapian directly for v2 Eric Wong
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: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210103020617.15719-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).