Create hashes using string builder instead of big integers about jimagehash HOT 5 CLOSED

for smaller than 64 bit hashes we could also fall back to long variables and do primitive bit shifting.

from jimagehash.

jmh benchmarks.
Big Integer is the current implementation. Performance decreases with increased hash length

Mutable big integer requires method handles and reflection access which is not warranted for the performance difference compare to the stringbuilder approach (as well as unit tests to guarantee that the implementation is working as expected).

A new StringBuilder is created for every hash creation. Caching a stringbuilder would result again in a performance gain at the cost of thread safety. In relation file IO is much more heavy and the treadoff isn't worth it.

Migration to either stringbuilder or mutable big int allows to cut the first pass needed to estimate the hash length on an algorithm basis

from jimagehash.

fixed with afc026d

from jimagehash.

Using a custom hash builder which manipulates a byte array directly we can gain even more performance d9ef1f8
Now even the 5000 bit hash runs with 13.000 hashes created / second up from 1.3 k

from jimagehash.

fixed with v 3.0.0

from jimagehash.