Change image hash compare algorithm and add multithreading #762
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #679
Closes #761
Helps #512
Algorithm performance for all similarity options should be very similar to fast compare option which become unnecessary and was removed.
Results should be a little worse than with previous algorithm, but scan speed boost especially with bigger similarities, should be clearly visible
Due using multi-threading, checking should be a lot of faster with bigger amount of files(0 similarity is special situation in which comparing images should happen almost instant), since most of operations are calculated on memory/CPU(without any disk operations)
Due removing Similarity enum, image cache file is not longer backward compatible, but still json config can be exported, changed manually and later imported to app(read docs for more info)
The only problem that I see is that I can't really test performance, because with ~8K images which I'm able to scan
With my testing on 20K images, new algorithm(4/8 processor) is a lot of faster than normal scan, but slightly less performant than fast compare