Closed Koeng101 closed 8 months ago
@Koeng101 that implementation is super naive and I'd recommend it be tuned up a little for performance before it being merged into main with things like what you're suggesting built on top of it. Check out details on #344.
This issue has had no activity in the past 2 months. Marking as stale
.
In my sequencing pipeline, currently the slowest part is the sequence mashing, running on one core. It would be nice to be able to do this concurrently, built in: because the primary use case is probably going to be mashing a LOT of sequences.
What I am specifically looking for: