From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jonathan Nieder <jrnieder@gmail.com>,
Lars Schneider <larsxschneider@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: USE_SHA1DC is broken in pu
Date: Thu, 23 Mar 2017 12:02:14 -0700 [thread overview]
Message-ID: <xmqqk27fddft.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170323174750.xyucxmfhuc6dbrzc@sigill.intra.peff.net> (Jeff King's message of "Thu, 23 Mar 2017 13:47:50 -0400")
Jeff King <peff@peff.net> writes:
> Side note: I also have a feeling that any operation that cares about
> non-object sha1 performance is probably ripe for other, bigger
> optimizations. If you update 300MB worth of index entries, then the
> cost of computing a checksum over it isn't a big deal. But if you have
> a 300MB index file and you update one entry (or you just want to read
> one entry), maybe we ought to consider solutions that don't involve
> the whole 300MB in the first place. I know that's a much harder change
> because it may involve new on-disk formats. But it seems like that's
> the right long-term path forward.
Yes ;-)
next prev parent reply other threads:[~2017-03-23 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 19:22 USE_SHA1DC is broken in pu Linus Torvalds
2017-03-16 19:41 ` Jeff King
2017-03-16 19:44 ` Linus Torvalds
2017-03-16 19:46 ` Junio C Hamano
2017-03-16 19:51 ` Linus Torvalds
2017-03-16 20:26 ` Linus Torvalds
2017-03-16 19:41 ` Junio C Hamano
2017-03-17 3:18 ` Lars Schneider
2017-03-17 3:32 ` Lars Schneider
2017-03-21 20:09 ` Johannes Schindelin
2017-03-21 20:16 ` Junio C Hamano
2017-03-22 14:32 ` Johannes Schindelin
2017-03-22 22:02 ` Jonathan Nieder
2017-03-23 16:43 ` Johannes Schindelin
2017-03-23 17:16 ` Linus Torvalds
2017-03-23 17:47 ` Jeff King
2017-03-23 19:02 ` Junio C Hamano [this message]
2017-03-23 22:22 ` Jonathan Nieder
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=xmqqk27fddft.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.