From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: Re: [PATCH 1/5] v2writable: fix batch size accounting
Date: Fri, 7 Aug 2020 13:13:09 +0000 [thread overview]
Message-ID: <20200807131309.GA3710@dcvr> (raw)
In-Reply-To: <20200807105218.16843-2-e@yhbt.net>
Eric Wong <e@yhbt.net> wrote:
> We need to account for whether shard parallelization is
> enabled or not, since users of parallelization are expected
> to have more RAM.
> ---
> lib/PublicInbox/V2Writable.pm | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/lib/PublicInbox/V2Writable.pm b/lib/PublicInbox/V2Writable.pm
> index a029fe4c..03320b9c 100644
> --- a/lib/PublicInbox/V2Writable.pm
> +++ b/lib/PublicInbox/V2Writable.pm
> @@ -152,6 +152,12 @@ sub add {
> $self->{ibx}->with_umask(\&_add, $self, $eml, $check_cb);
> }
>
> +sub batch_bytes ($) {
> + my ($self) = @_;
> + $self->{parallel} ? $PublicInbox::SearchIdx::BATCH_BYTES
> + : $PublicInbox::SearchIdx::BATCH_BYTES * $self->{shards};
> +}
Oops, that was backwards :x Will squash this in:
diff --git a/lib/PublicInbox/V2Writable.pm b/lib/PublicInbox/V2Writable.pm
index 03320b9c0..f7a318e5b 100644
--- a/lib/PublicInbox/V2Writable.pm
+++ b/lib/PublicInbox/V2Writable.pm
@@ -154,8 +154,8 @@ sub add {
sub batch_bytes ($) {
my ($self) = @_;
- $self->{parallel} ? $PublicInbox::SearchIdx::BATCH_BYTES
- : $PublicInbox::SearchIdx::BATCH_BYTES * $self->{shards};
+ ($self->{parallel} ? $self->{shards} : 1) *
+ $PublicInbox::SearchIdx::BATCH_BYTES;
}
# indexes a message, returns true if checkpointing is needed
> sub do_idx ($$$$) {
> my ($self, $msgref, $mime, $smsg) = @_;
> @@ -160,7 +166,7 @@ sub do_idx ($$$$) {
> my $idx = idx_shard($self, $smsg->{num} % $self->{shards});
> $idx->index_raw($msgref, $mime, $smsg);
> my $n = $self->{transact_bytes} += $smsg->{raw_bytes};
> - $n >= ($PublicInbox::SearchIdx::BATCH_BYTES * $self->{shards});
> + $n >= batch_bytes($self);
> }
...Because the old code always assumed parallel shards (even
with --jobs=0).
> sub _add {
> @@ -1195,7 +1201,7 @@ sub index_xap_step ($$$;$) {
> my $ibx = $self->{ibx};
> my $all = $ibx->git;
> my $over = $ibx->over;
> - my $batch_bytes = $PublicInbox::SearchIdx::BATCH_BYTES;
> + my $batch_bytes = batch_bytes($self);
> $step //= $self->{shards};
> my $end = $sync->{art_end};
> if (my $pr = $sync->{-opt}->{-progress}) {
And the new index_xap_step was not designed for parallel
operation, initially.
next prev parent reply other threads:[~2020-08-07 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 10:52 [PATCH 0/5] more indexing improvements Eric Wong
2020-08-07 10:52 ` [PATCH 1/5] v2writable: fix batch size accounting Eric Wong
2020-08-07 13:13 ` Eric Wong [this message]
2020-08-07 10:52 ` [PATCH 2/5] index: --compact respects --sequential-shard Eric Wong
2020-08-07 10:52 ` [PATCH 3/5] index: max out XAPIAN_FLUSH_THRESHOLD if using --batch-size Eric Wong
2020-08-07 10:52 ` [PATCH 4/5] searchidx: use Perl truthiness to detect XAPIAN_FLUSH_THRESHOLD Eric Wong
2020-08-07 10:52 ` [PATCH 5/5] index: add built-in --help / -? 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 \
--in-reply-to=20200807131309.GA3710@dcvr \
--to=e@yhbt.net \
--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.
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).