Skip to content
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 fix #24

Open
mjsull opened this issue Feb 21, 2020 · 1 comment
Open

memory fix #24

mjsull opened this issue Feb 21, 2020 · 1 comment

Comments

@mjsull
Copy link

mjsull commented Feb 21, 2020

Sorry if I have misunderstood what the program is doing.

From what I can tell, prophex is storing all the results from each query in memory and then dumping them to STDOUT once the software has ended. For very large read files, this means prophex is using a lot of memory it doesn't need to. Would it not be better to dump each read to STDOUT as the results come in?

@karel-brinda
Copy link
Member

@salikhov-kamil would be in a better position to answer this. As far as I understand this part, ProPhex uses the BWA parallelization engine based on klib. It shouldn't be storing all the data in memory, but rather do buffering (since the output data are generated in different threads, this is necessary). The data may be indeed be printed in batches, but this definitely shouldn't cause storing all output data in memory (unless it's a very small dataset). However, all these things are always dependent on the specific settings of various parameters in the program so I would like to double-check. Do you have a specific example which suggests that everything is stored in memory till the end and printed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants