Closed cmaceves closed 1 year ago
@cmaceves we switched to ivar 1.3.2 last week and noticed it was taking 10x (!) longer to run on our 384 samples (~1 M reads each).
Would this bug explain the slowdown in ivar trim?
hi @tseemann! that's correct, it is causing the slowdown. we're aiming for a fast turn around time on 1.3.3 to address that oversight.
addressed in PR #155
In the code for primer trimming insertionSort gets called every time get_overlapping_primers is called, creating a slowdown
This should only be called once.