From: Eric Wong <e@80x24.org>
To: workflows@vger.kernel.org, meta@public-inbox.org
Subject: Re: WIP: searching all of lore
Date: Tue, 8 Dec 2020 18:02:32 +0000 [thread overview]
Message-ID: <20201208180232.GA20637@dcvr> (raw)
In-Reply-To: <20201208140111.3lxecf42d6ooskeb@chatter.i7.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Sat, Dec 05, 2020 at 08:07:17PM +0000, Eric Wong wrote:
> > Per-inbox search also uses subset search, so all the existing
> > inboxes should be searchable on an individual level, not just /all:
> > http://rskvuqcfnfizkjg6h5jvovwb3wkikzcwskf54lfpymus6mxrzw67b5ad.onion/lkml/
> > http://rskvuqcfnfizkjg6h5jvovwb3wkikzcwskf54lfpymus6mxrzw67b5ad.onion/workflows/
> > http://rskvuqcfnfizkjg6h5jvovwb3wkikzcwskf54lfpymus6mxrzw67b5ad.onion/netdev/
>
> So, are things to the point where we only need a single xapian db for
> all lists, or do we still need to keep individual list indexes?
Only indexlevel=basic (sqlite) for individual lists. This saves
a bunch of FDs and provides ~60G overall space savings (not compacted).
For all of lore:
git + {over,msgmap}.sqlite3: 51G
extindex "all" over.sqlite3 + Xapian: 193G
next prev parent reply other threads:[~2020-12-08 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 19:45 WIP: searching all of lore Eric Wong
2020-11-28 22:34 ` Eric Wong
2020-12-05 20:07 ` Eric Wong
2020-12-08 14:01 ` Konstantin Ryabitsev
2020-12-08 18:02 ` Eric Wong [this message]
2020-12-08 18:11 ` Konstantin Ryabitsev
2020-12-01 14:00 ` Konstantin Ryabitsev
2020-12-01 18:48 ` Eric Wong
2021-03-17 7:11 ` Eric Wong
2021-03-17 13:27 ` Konstantin Ryabitsev
2021-03-17 18:18 ` Eric Wong
2021-03-17 18:37 ` Konstantin Ryabitsev
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=20201208180232.GA20637@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=workflows@vger.kernel.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).