diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2015-10-16 12:05:58 -0700 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2015-10-16 12:07:07 -0700 |
| commit | 0cb602e33aa4972170fa676547e4dd8dca63c00c (patch) | |
| tree | f368e040b189e7a2c6c80c3668a1077842f667c6 | |
| parent | e8d7e205309c05cf2c7c9a42b33708b1eb4587ca (diff) | |
| download | coreutils-0cb602e33aa4972170fa676547e4dd8dca63c00c.tar.xz | |
doc: remove obsolete performance comment
sha512sum can be faster than sha256sum.
E.g., ‘dd if=/dev/zero bs=1024k count=1024 | time sha256sum’
reports 8.16 user CPU seconds on my host, whereas sha512sum
consumes 5.45 seconds (Fedora x86-64 on an AMD Phenom II X4 910e).
Although sha512sum is still considerably slower on x86, a good
chunk of uses are on 64-bit hosts and anyway there’s little point
to scaring people away from sha512sum nowadays.
* doc/coreutils.texi (sha2 utilities): Remove obsolete comment.
| -rw-r--r-- | doc/coreutils.texi | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi index a029ec6c8..c988aca4f 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -3948,9 +3948,6 @@ these commands are precisely the same as for @command{md5sum} and @command{sha1sum}. @xref{md5sum invocation}. -Note: The SHA384 and SHA512 digests are considerably slower to -compute, especially on 32-bit computers, than SHA224 or SHA256. - @node Operating on sorted files @chapter Operating on sorted files |