user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH 0/2] index: support --compact / -c
Date: Sat, 28 Mar 2020 00:56:02 +0000	[thread overview]
Message-ID: <20200328005604.17573-1-e@yhbt.net> (raw)

It looks like HDDs and SSDs have gotten and will get even more
expensive due to manufacturing freezes from the pandemic.

Indexing (especially with --reindex to fixup old bugs) takes a
large amount of space, so support running compact immediately
after indexing to avoid users having to script a -compact
invocation for each inbox.  Compacting before indexing can be
triggered by using this switch twice, to further reduce space
overhead at a small time loss.

Note: I only found the bug fixed in 1/2 while testing 2/2.  It
took me a while to fix this bug because I've probably lost 10
IQ points from the stress of recent weeks :<

Eric Wong (2):
  searchidxshard: ensure we set indexlevel on shard[0]
  index: support --compact / -c on command-line

 Documentation/public-inbox-index.pod | 24 ++++++++++++++++++++----
 lib/PublicInbox/InboxWritable.pm     |  1 +
 lib/PublicInbox/SearchIdx.pm         | 26 +++++++++++++++++---------
 lib/PublicInbox/SearchIdxShard.pm    |  4 +++-
 lib/PublicInbox/Xapcmd.pm            |  4 +++-
 script/public-inbox-index            | 20 +++++++++++++++++---
 t/convert-compact.t                  | 13 +++++++++++++
 t/init.t                             |  7 ++++++-
 8 files changed, 80 insertions(+), 19 deletions(-)

             reply	other threads:[~2020-03-28  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28  0:56 Eric Wong [this message]
2020-03-28  0:56 ` [PATCH 1/2] searchidxshard: ensure we set indexlevel on shard[0] Eric Wong
2020-03-28  0:56 ` [PATCH 2/2] index: support --compact / -c on command-line 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=20200328005604.17573-1-e@yhbt.net \
    --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.
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).