From: Eric Wong <firstname.lastname@example.org> To: email@example.com Subject: [PATCH 0/4] xcpdb: support resharding Xapian DBs Date: Fri, 14 Jun 2019 03:03:14 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Defaulting the number of Xapian shards based on the number of CPUs can be detrimental to performance given the lack of speed in common storage systems; since NVMe speeds are not yet common. To help public-inbox users recover from this inefficiency while allowing continuous email archival, we can support arbitrary resharding to have fewer shards (or more, if doing HW upgrades). Note: I'm also going to move the documentation towards using the word "shard" (instead of "partition") to be consistent with current Xapian documentation (1.4+, and "master"). Xapian 1.2 did not use the word "shard" at all, but IME from my interactions with non-Xapian search engine folks, the word "shard" is pretty common. Eric Wong (4): v2writable: use a smaller default for Xapian partitions xapcmd: preserve indexlevel based on the destination xcpdb: use destination shard as progress prefix xcpdb: support resharding v2 repos Documentation/public-inbox-xcpdb.pod | 11 ++ MANIFEST | 1 + lib/PublicInbox/V2Writable.pm | 18 ++- lib/PublicInbox/Xapcmd.pm | 222 +++++++++++++++++++++------ script/public-inbox-xcpdb | 4 +- t/xcpdb-reshard.t | 83 ++++++++++ 6 files changed, 286 insertions(+), 53 deletions(-) create mode 100644 t/xcpdb-reshard.t -- EW
next reply other threads:[~2019-06-14 3:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-14 3:03 Eric Wong [this message] 2019-06-14 3:03 ` [PATCH 1/4] v2writable: use a smaller default for Xapian partitions Eric Wong 2019-06-14 3:03 ` [PATCH 2/4] xapcmd: preserve indexlevel based on the destination Eric Wong 2019-06-14 3:03 ` [PATCH 3/4] xcpdb: use destination shard as progress prefix Eric Wong 2019-06-14 3:03 ` [PATCH 4/4] xcpdb: support resharding v2 repos 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: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/4] xcpdb: support resharding Xapian DBs' \ /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
Code repositories for project(s) associated with this 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).