Concurrency for `ivar trim`? about ivar

[cmaceves]

@khyox hey! I'm caught up in doctorate applications at the moment, we're anticipating a release in December before the holiday season

[cmaceves]

hi @khyox thank you, it went well. we're in the process of doing some final code reviews prior to release, it's still imminent!

[cmaceves]

Hi! Not the immediate future. Is there a specific case or dataset you have where you feel that would be vital? (ie. are you running into issues where process time is too long in the current implementation)

[philiptzou]

@cmaceves Thanks for the quick response. No I didn't run into any issues - but just discovered iVar is the slow bottleneck in our pipeline and I found the CPU usage of iVar never exceeds 100% (top -c).

I can imagine it is practical to use multiple CPUs to process a BAM file includes short reads, since you can just make chunks and deliver the chunks to sub-workers. That's the reason why I ask if you have plan to do so.

[cmaceves]

@philiptzou Yeah - I agree that definitely seems within reason and practical as a feature request for future implementation. We're getting ready for a release in the next month or so, but will keep this in mind for future milestones. Thanks for brining this to our attention!

[philiptzou]

@cmaceves Thank you!

[khyox]

(...) We're getting ready for a release in the next month or so, but will keep this in mind for future milestones. (...)

Hi @cmaceves. Are you still planning an imminent new release? Thanks!

[khyox]

Great news!! Thank you very much @cmaceves and best of luck with the applications! :)

[khyox]

Hey @cmaceves! Hope you were lucky with your PhD applications.
I guess the release plans got delayed somehow. Are you still planning a new version soon? Thanks!

[khyox]

Both great news! :) Thank you so much @cmaceves!