From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: lei-managed pseudo mailing lists
Date: Mon, 26 Apr 2021 20:34:28 +0000 [thread overview]
Message-ID: <20210426203428.GA5692@dcvr> (raw)
In-Reply-To: <20210426194659.d5w2nkeqvtyni4ay@nitro.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> I'm just worried that if we overuse the alternates, then we may find ourselves
> in a situation where when we repack the "every blob" shared repository, we'll
> end up with a pack that isn't really optimized to be used by any of the
> member repos. So, in a situation where a clone is performed, git-upload-pack
> will have to spend a lot of cycles navigating through the monstrous parent
> pack just to build and re-compress the small subset of objects it needs to
> send.
>
> Git has ways of dealing with this by allowing to set things like pack islands,
> but it's finicky and requires that each child repo is defined as refs in the
> parent repo. We deal with this in grokmirror, but it's messy and requires
> properly tracking child repo additions/removals/etc.
At least for personal use, I've been meaning to look into
automatically managing islands.
> I think it may be one of those cases where wasting disk space on duplicate
> objects is worth the CPU cycle savings.
Agreed for serving public inboxes.
> On Mon, Apr 26, 2021 at 06:47:17PM +0000, Eric Wong wrote:
> > The aforementioned maxuid prevents stuff that's too old from
> > being seen. Otherwise, there's always "public-inbox-learn rm".
>
> How would it handle the situation where we import a new list into lore with a
> 10-year-long archive of messages?
maxuid is either per-inbox or per-extindex.
If the search is going off of inboxes via --only, then it would
not see the new inbox at all. If it's on an extindex like
"all", then yes, the newly-imported historical messages would
show up.
So using "rt:" (Received time) is helpful in the [extindex "all"] case
Also, the approxidate parsing is done every time with "lei up",
so you can have a rolling window with "rt:last.week.." as a
search parameter.
prev parent reply other threads:[~2021-04-26 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 16:44 lei-managed pseudo mailing lists Konstantin Ryabitsev
2021-04-26 17:37 ` Eric Wong
2021-04-26 18:20 ` Konstantin Ryabitsev
2021-04-26 18:47 ` Eric Wong
2021-04-26 19:46 ` Konstantin Ryabitsev
2021-04-26 20:34 ` Eric Wong [this message]
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=20210426203428.GA5692@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.
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).