From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH 1/5] inbox: delay ->version detection
Date: Mon, 21 Dec 2020 18:54:17 +0000 [thread overview]
Message-ID: <20201221185417.GA30275@dcvr> (raw)
In-Reply-To: <20201221075122.1587-2-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> Our read-only code won't need to know the version until an inbox
> is accessed. This is a small step towards eliminating many
> stat() calls on read-only daemon startup.
This actually brings a no-op PublicInbox::Config->new->each_inbox(sub {})
from ~20s to ~5s on an SSD with 50K tiny inboxes.
Not exactly a small step :>
next prev parent reply other threads:[~2020-12-21 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 7:51 [PATCH 0/5] extindex->misc prep stuff Eric Wong
2020-12-21 7:51 ` [PATCH 1/5] inbox: delay ->version detection Eric Wong
2020-12-21 18:54 ` Eric Wong [this message]
2020-12-21 7:51 ` [PATCH 2/5] isearch: use numeric sort for article numbers Eric Wong
2020-12-21 7:51 ` [PATCH 3/5] use rel2abs_collapsed when loading Inbox objects Eric Wong
2020-12-21 7:51 ` [PATCH 4/5] searchidx: rename get_val to int_val and return IV Eric Wong
2020-12-21 7:51 ` [PATCH 5/5] extsearch*: drop unnecessary path canonicalization 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=20201221185417.GA30275@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).