-
Notifications
You must be signed in to change notification settings - Fork 14
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
Logging performance of de novo variant discovery with racon #303
Comments
@mbhall88 could you also please report the max RAM usage? I am quite concerned with this part in This is a dictionary from loci names to the subreads that map to each locus, inferred by |
The nanopore runtime and memory usage of drprg with the previous version of de novo discovery and the Illumina Pandora is the vast majority of runtime and memory in drprg so these act as good benchmark figures, especially given the only thing that will change between them is the pandora version |
I just finished running Paper run
commit 02f9ec
I think runtime is totally fine, we got almost the same exact runtime. RAM usage is much higher though, probably related to this: #303 (comment) . It will be the RAM bottleneck of the pipeline ( OFC this is data dependent, so let's see how @mbhall88 benchmarks compare |
This RAM use is, IMO, acceptable for the moment - i wouldn't postpone the merge to reduce RAM |
Okay, so here are the updated benchmark figures RuntimeIlluminaMedian is 91s, down from 98s. So it is faster now on Illumina! NanoporeMedian is now 171s, up from 163s. MemoryIlluminaMedian is 46MB, down from 54MB, so Memory is marginally down too. NanoporeMedian is now 270MB, up from 240MB. All in all, I think this acceptable. |
To be done by @mbhall88 . Could you please use this commit?
The text was updated successfully, but these errors were encountered: