Feature #2899
open
DigestSha256 vs CRC-32C
0%
Description
(Originally reported by Gordon Irlam)
Signature type DigestSha256. Cryptographic robustness isn't necessary for integrity protection, and comes at great cost. A quick test shows that Sha256 only runs at around 250Mbytes/sec on a current generation single core. Thanks in part to a special instruction on the same core, CRC32C runs at around 24Gbytes/sec. The use case for dispensing with provenance protection is likely to be the need for high performance. I would therefore suggest considering adding CRC32C to the spec, and possibly removing DigestSha256.
Updated by Davide Pesavento almost 9 years ago
- Subject changed from DigestSha256 vs CRC32C to DigestSha256 vs CRC-32C
Updated by Tai-Lin Chu almost 9 years ago
If the purpose is just integrity verifying, crc32 does the job in a much faster way (If your chip supports SSE 4.2, it is even faster). It will be good to see digestSHA256 be replaced by crc32c. (go-ndn implemented this a couple months ago.)