From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Has anyone tried importing lkml?
Date: Mon, 15 Jan 2018 13:04:48 -0500 [thread overview]
Message-ID: <dd40474c-e468-584c-391e-1e9d252ff28c@linuxfoundation.org> (raw)
In-Reply-To: <20180115175534.GA5787@80x24.org>
On 2018-01-15 12:55 PM, Eric Wong wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>> The question I do have is whether public-inbox is the right tool for
>> doing something like this. LKML message count is somewhere in the
>> millions, and I'm curious what that would look like when imported into a
>> git tree used by public-inbox. For comparison, the Linux kernel itself
>> is only about 700,000 commits, so a git repo of all LKML archives would
>> easily dwarf that.
>
> It's probably too slow for object walking (which impacts
> clone-ability) at the moment due to tree object churn. The
> current 2/38 tree structure (which mirrors git loose objects)
> turned out to be a not-so-great idea; maybe 2/2/36 would be
Does frequent repacking with --write-bitmap-index help at all? The
bitmaps usually dramatically improve cloning speeds for us.
Best,
--
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
next prev parent reply other threads:[~2018-01-15 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 17:41 Has anyone tried importing lkml? Konstantin Ryabitsev
2018-01-15 17:55 ` Eric Wong
2018-01-15 18:04 ` Konstantin Ryabitsev [this message]
2018-01-15 18:27 ` Eric Wong
2018-01-15 20:09 ` Konstantin Ryabitsev
2018-01-15 20:42 ` Bram Adams
2018-01-15 20:54 ` Konstantin Ryabitsev
2018-01-15 21:03 ` Bram Adams
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=dd40474c-e468-584c-391e-1e9d252ff28c@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=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).