Give kraken2 100G from 100MB input#1606
Give kraken2 100G from 100MB input#1606mira-miracoli wants to merge 1 commit intousegalaxy-eu:masterfrom
Conversation
|
I don't see in your screenshot where the data is coming from. A similar figure I know does not take the input size into consideration. You just see that 14% of all jobs finish with less then 30GB of memory, 30% of all jobs with less then 100GB of memory ... etc |
|
|
|
Hi there @mira-miracoli - the RAM requirement is more connected to the DB size than the input size. Since the kraken2 wrapper pulls the DB location from a tool data table, I am not sure if this is included in the input size? Thus, for the 8.1 GB Mycobacterium database, 10 GB is enough, for the 94 GB "standard" database, 100 GB works. So the challenge then becomes: how to access this information? Right now kraken2 relies on the In the future, kraken2 could have the database passed as an input (galaxyproject/tools-iuc#7257) in which case the size of the database input could be used. I am very naive when it comes to TPV, so please let me know if this line of thinking makes sense. |
|
I see, maybe we can wait then for this to happen:
I think it could access this file, but could it slow down the job handlers maybe? |
|
I have this here for a TPV rule. @pvanheus wanted to look at it: |
I think I need some help with the interpretation of my analysis :D
This means, that on average 1GB of input needed 506GB of memory?