From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] minor cat-file optimizations
Date: Wed, 18 May 2016 12:52:53 -0400 [thread overview]
Message-ID: <20160518165253.GA5379@sigill.intra.peff.net> (raw)
At Git Merge, Charles suggested that "--buffer" should be the default
for "--batch-all-objects". This bit me again yesterday, so I thought I'd
actually implement it. :)
That's in the second patch. The first one is another micro-optimization
that happens to help the use case I was working on (the speedup there is
"only" 40%, but the case I was looking at had a pathological number of
packs, and so was even slower).
[1/2]: cat-file: avoid noop calls to sha1_object_info_extended
[2/2]: cat-file: default to --buffer when --batch-all-objects is used
-Peff
next reply other threads:[~2016-05-18 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 16:52 Jeff King [this message]
2016-05-18 16:54 ` [PATCH 0/2] minor cat-file optimizations Jeff King
2016-05-18 16:55 ` [PATCH 1/2] cat-file: avoid noop calls to sha1_object_info_extended Jeff King
2016-05-18 16:56 ` [PATCH 2/2] cat-file: default to --buffer when --batch-all-objects is used Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160518165253.GA5379@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@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 NNTP newsgroup(s).