mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: How expensive is verification anyway?

Browse source
This commit is contained in:
https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd 2018-03-13 17:58:19 +00:00 • committed by admin
parent e16b069331
commit 7ea75e1132
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/todo/support_disabling_verification_of_transfer_over_p2p_protocol/comment_1_70840f9fc06f2f111f89d5b6cf6ad7e0._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="https://openid.stackexchange.com/user/3ee5cf54-f022-4a71-8666-3c2b5ee231dd"
nickname="Anthony DeRobertis"
avatar="http://cdn.libravatar.org/avatar/1007bfece547e9f2d86fafa142cd240a62456c37f104a9d96ba9db5bf18e1934"
subject="How expensive is verification anyway?"
date="2018-03-13T17:58:19Z"
content="""
A quick check with `openssl speed -evp sha256` (and `-evp sha512`) shows SHA-256 is ~210MB/sec and SHA-512 ~275MB/sec on my not that recent i7 930. I'm sure its more of an issue on embedded or phones... but there of course the network is often slower. If the hash is faster than the transfer, seems like it shouldn't really cause that much of a slowdown (unless I guess its competing with ssh for CPU time, but that seems unlikely on multi-core machines).
I wonder if a easier way to speed it up wouldn't be to support BLAKE2 as a backend. Wouldn't help with existing hash keys, of course (without a migrate).
"""]]