From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH 0/7] index + extindex interaction improvements
Date: Fri, 25 Dec 2020 10:39:40 +0000 [thread overview]
Message-ID: <20201225103940.GA8814@dcvr> (raw)
In-Reply-To: <20201225102115.6745-1-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> Some things which make -index less painful when auto-updating
> external indices.
>
> "public-inbox-extindex --all" itself is still painfully slow
> with 50K inboxes, but I think that can only be used once for
> initialization and -index can be relied on for all incremental
> updates.
I've been wondering if --watch mode (using inotify) might be a
good idea for indexing in mirrors, too (or with -mda).
This would especially be helpful for those who want to keep
extindex directories owned by a separate user than the one
who writes to inboxes.
next prev parent reply other threads:[~2020-12-25 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 10:21 [PATCH 0/7] index + extindex interaction improvements Eric Wong
2020-12-25 10:21 ` [PATCH 1/7] index: disable --fast-noop on --reindex Eric Wong
2020-12-25 10:21 ` [PATCH 2/7] extsearchidx: delay SQLite availability checks Eric Wong
2020-12-25 10:21 ` [PATCH 3/7] extsearchidx: close DB handles after use if FD constrained Eric Wong
2020-12-25 10:21 ` [PATCH 4/7] index: do not attach inbox to extindex unless updated Eric Wong
2020-12-25 10:21 ` [PATCH 5/7] index: fix --no-fsync flag propagation to extindex Eric Wong
2020-12-25 10:21 ` [PATCH 6/7] v2writable: don't verify tip if reindexing Eric Wong
2020-12-25 10:21 ` [PATCH 7/7] index: filter out indexlevel=basic from extindex Eric Wong
2020-12-25 10:39 ` Eric Wong [this message]
2020-12-26 1:44 ` [PATCH 0/3] extindex --watch support Eric Wong
2020-12-26 1:44 ` [PATCH 1/3] default to CORE::warn in $SIG{__WARN__} handlers Eric Wong
2020-12-26 1:44 ` [PATCH 2/3] extindex: --watch for inotify-based updates Eric Wong
2020-12-26 1:44 ` [PATCH 3/3] init: use the return value of rel2abs_collapsed 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=20201225103940.GA8814@dcvr \
--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).