From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2016, #08; Wed, 24)
Date: Wed, 24 Aug 2016 15:01:21 -0700 [thread overview]
Message-ID: <xmqqpooxomha.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160824213450.eo6hlmt4oly6gwih@sigill.intra.peff.net> (Jeff King's message of "Wed, 24 Aug 2016 17:34:50 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Aug 24, 2016 at 02:16:02PM -0700, Junio C Hamano wrote:
>
>> * jk/pack-objects-optim-mru (2016-08-11) 4 commits
>> (merged to 'next' on 2016-08-11 at c0a7dae)
>> + pack-objects: use mru list when iterating over packs
>> + pack-objects: break delta cycles before delta-search phase
>> + sha1_file: make packed_object_info public
>> + provide an initializer for "struct object_info"
>>
>> "git pack-objects" in a repository with many packfiles used to
>> spend a lot of time looking for/at objects in them; the accesses to
>> the packfiles are now optimized by checking the most-recently-used
>> packfile first.
>>
>> Will hold to see if people scream.
>
> Just a note that we've been running with this at GitHub on all of our
> servers for a bit over a week, and no screaming yet. That's not
> necessarily proof of anything, but it does make the audience of "people"
> a bit bigger than just "next", as we run quite a few invocations of
> pack-objects in a day.
>
> I don't think that changes anything in the near future, since this is
> obviously not for v2.10, but barring any complaints, it's probably a
> reasonable topic to consider for the version after (and of course I'll
> relay any issues we come across on our servers).
Yeah, that "Will hold" is primarily me being lazy [*1*] during the
-rc period when updating the "What's cooking". After following the
"break delta cycles" patch carefully, I am no longer worried about
this topic. It should be in 'master' early in the next cycle, among
other topics that are competently done.
> I'm planning to deploy the delta-cache topic soon, too, so that should
> give it some good exercise.
Good. Thanks.
[Footnote]
*1* ... and a bit more careful, as any "Will merge to 'next'" thing
gets marked as "Will merge to 'master'" by default and having any
entry under "Will merge to 'master'" in "Meta/cook -w" report tempts
me to merge them even during -rc period.
next prev parent reply other threads:[~2016-08-24 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 21:16 What's cooking in git.git (Aug 2016, #08; Wed, 24) Junio C Hamano
2016-08-24 21:34 ` Jeff King
2016-08-24 22:01 ` Junio C Hamano [this message]
2016-08-26 14:09 ` Johannes Schindelin
2016-08-26 16:04 ` Junio C Hamano
2016-08-31 5:10 ` Stefan Beller
2016-08-31 6:25 ` Jacob Keller
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://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpooxomha.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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/mirrors/git.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).