You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using StringCRC is actually quite bad for calculating a hash of the data, as 1 states
CRC-32 poses the highest risk for hash collisions. This hash function is generally not recommended for use. If a hub were to contain 77,163 hash values, the chance of a hash collision occurring is 50%, which is extremely high compared to other methods.
Using StringCRC is actually quite bad for calculating a hash of the data, as 1 states
AllenInstitute/mies-utils-xop#1 has a WIP branch with XXH32 from 2 which has the following performance characteristics.
gives
so while a tiny bit slower than CRC32 this is much faster as the other hash algorithms.
Adding this new hash would also allow us to move to XXhash from SHA* where we don't need cryptographic hashes.
The text was updated successfully, but these errors were encountered: