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

running time too long #153

Open
nsuarezg opened this issue Nov 8, 2023 · 4 comments
Open

running time too long #153

nsuarezg opened this issue Nov 8, 2023 · 4 comments

Comments

@nsuarezg
Copy link

nsuarezg commented Nov 8, 2023

hello, I am looking for help regarding the use of KrakenUniq. I am planning to run samples containing between 20 and 40.10E6 reads (150PE) using the MicrobialDB. According to my first trial and estimations, each sample will take between 10 and 20 days to be classify. The same samples only need a few hours run when using Kraken2. I am copying the DB to the local disk before the run and use the script below. Can you help me in order to decrease the calculation time? Thank you in advance.
Nathalie

image

@salzberg
Copy link
Collaborator

salzberg commented Nov 8, 2023

You probably don't have enough RAM on your computer to load the DB, which forces it to swap. This can take forever (or 100s of times longer). First make sure you have enough RAM (should be larger than the DB) and also try adding the parameter --preload to your krakenuniq command. That will force it to load the whole DB in memory.

@nsuarezg
Copy link
Author

nsuarezg commented Nov 8, 2023

Thank you for your reply. I have enough RAM. The DB is copied and extracted without any problem (takes 2h). But then the classification takes forever (for instance 1h to classify 2,4Mb files (80.000 reads)). I tried the --preload, but it did not improve the process.

@salzberg
Copy link
Collaborator

salzberg commented Nov 8, 2023

this should only take a minute to classify. You might have enough RAM but your OS might be set so that you can only use 50% of it for 1 process - this is the default for many Unix installations. You could turn off swap (requires a reboot). Or try using --preload-size and only give it, say, much less than 50% of the RAM you think you have. I'd recommend trying 32G first, see how that works. You didn't say how much RAM you have so I'm guessing.

@nsuarezg
Copy link
Author

nsuarezg commented Nov 8, 2023

Thank you again. I will try and come back to you :-)

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