-
Notifications
You must be signed in to change notification settings - Fork 0
Memory testing #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory testing #40
Conversation
…updates in minmap2-rs Add bare clipppy allows cause I need this backed up
Kept the Py<PyAny> wrapper that messes the memory up but no leaks
Currently pointing at the revision commit hash 037abe5 When crates is updated, will come back and repoint at that
Was failing the tests as Multiple handlers were being set Remove mem::drop on aligners in tests
Stop it being tested by pytest
As fun as MSRV roulette was turning out to be
Bump version Add more classifiers Add Readme.md
This release switches from spawning threads every time adds some complexity in passing reads into the threadpool via an ArrayQueue and then transferring them back to Some unused methods are added for catching memory leaks, which I intend to implement in PyTest. These are |
Blocked, waiting on jguhlin/minimap2-rs#40 to be merged.
This PR rewrites the thread pool to be a permanently waiting pool, rather than spawning a new pool each
map_batch
call.An improvement to be made would be to park the threads, rather than sleep them but the effect is the same.
There is some memory weirdness around using
Py<PyAny>>
to store the Dictionary on the sideWaiting until the minimap2-rs crate is updated as currently references a local version that only exists on my laptop.