Re: Which hash function to use, was Re: RFC: Another proposed hash function transition plan

From: Jeff King <peff@peff.net>
Date: Jun 16, 2017, 20:42 UTC
Message-ID: <20170616204208.ak5twydrloxefm42@sigill.intra.peff.net>
In-Reply-To: <alpine.DEB.2.21.1.1706161438470.4200@virtualbox>

On Fri, Jun 16, 2017 at 03:24:19PM +0200, Johannes Schindelin wrote:

> I have no doubt that Visual Studio Team Services, GitHub and Atlassian
> will eventually end up with FPGAs for hash computation. So that's that.

I actually doubt this from the GitHub side. Hash performance is not even on our radar as a bottleneck. In most cases the problem is touching uncompressed data _at all_, not computing the hash over it (so things like reusing on-disk deltas are really important).

-Peff

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.