This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients SilentGhost, christian.heimes, gregory.p.smith, martin.panter, palaviv, rhettinger, terry.reedy, vstinner
Date 2016-03-31.20:10:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459455057.56.0.865804214112.issue26488@psf.upfronthosting.co.za>
In-reply-to
Content
Threading doesn't make much sense here. The runtime of hash computation is usually dominated by I/O performance. On a typical consumer computer SSDs have a sequential read performance of 200 to 500 MiB/sec. SHA-512 performance between 100 to 150 Mib/sec. Threading could make parallel computation a bit faster, but at the cost of a much more complex implementation. Let's keep it simple.

Both Python's hashlib implementation and OpenSSL aren't the best foundation if you are aiming for maximum performance. All libraries do couple of malloc()s, memcpy() and have additional overheads, too.

And please don't use MD5 in your examples. Go for sha256.
History
Date User Action Args
2016-03-31 20:10:57christian.heimessetrecipients: + christian.heimes, rhettinger, terry.reedy, gregory.p.smith, vstinner, SilentGhost, martin.panter, palaviv
2016-03-31 20:10:57christian.heimessetmessageid: <1459455057.56.0.865804214112.issue26488@psf.upfronthosting.co.za>
2016-03-31 20:10:57christian.heimeslinkissue26488 messages
2016-03-31 20:10:57christian.heimescreate