The SHA1 replacement plan

Josef 'Jeff' Sipek jeffpc at josefsipek.net
Tue Jul 28 19:02:46 UTC 2020


On Sun, Jul 26, 2020 at 18:26:51 +0200, Joerg Sonnenberger wrote:
...
> I've attached basic benchmark numbers below. The asm variant is using
> whatever my Threadripper supports in terms of low-level primitives, e.g.
> AVX2 and the SHA extension, either from OpenSSL (BLAKE2, SHA2, SHA3) or
> the reference implementations (K12, BLAKE3, BLAKE3*). Test case was
> hashing a large file (~7GB). 

While these performance measurements are important, it is also important to
make sure that older (or less "top of the line") hardware isn't completely
terrible.  For example, it is completely reasonable (at least IMO) to still
use a Sandy Bridge-era CPUs.  Likewise, it is reasonable to run hg on a
embedded system (although those tend to have wimpy I/O as well).

Anyway, thanks for spending time on this!

Jeff.

-- 
All parts should go together without forcing.  You must remember that the
parts you are reassembling were disassembled by you.  Therefore, if you
can’t get them together again, there must be a reason.  By all means, do not
use a hammer.
		— IBM Manual, 1925



More information about the Mercurial-devel mailing list