[MRG] Improving intersection and union calculations #1475
Merged
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.
Playing a bit with the
intersection()
andintersection_size()
methods in Rust. I started looking into this because of #1474 #1392 and the nagging suspicion that the calls to.merge
were making the performance worse. I isolated the.merge()
call for num MH sketches, and started working on scaled MH sketches first (because they are easier to reason about).In order to measure it, I created two new benchmarks (run with
cargo bench -- minhash
).This is the baseline (
latest
):For the first try, I created an
Union
iterator, similar to the currentIntersection
iterator:This is already pretty good, but it ends up iterating twice over the data.
The second try is an unrolled version (combining the
Intersection
andUnion
iterators, and keeping only data we need):Twice as fast, nice.
So, I tried to run
gather
from https://github.com/luizirber/sourmash_resources, and...It's pretty similar to the
latest
results 😂So, the problem is in other places, but might as well merge this eventually because it is faster in microbenchmarks? =P