Use @ADDMEMORY@ / @ADDTHREADS@ macros appropriately across samtools c…#7902
Use @ADDMEMORY@ / @ADDTHREADS@ macros appropriately across samtools c…#7902wm75 wants to merge 2 commits intogalaxyproject:mainfrom
Conversation
|
For the record: The tool that stands out as requiring fixing is arriba, which hard-codes memory usage of samtools sort thread, but determines threads from GALAXY_SLOTS. |
| | samtools fixmate -@ \$addthreads -u - - | ||
| | samtools sort -@ \$addthreads -m \${GALAXY_MEMORY_MB:-768}M -T "\${TMPDIR:-.}" -o '${output_bam}' | ||
| | samtools fixmate -@ \$addthreads -u - - | ||
| | samtools sort -@ \$addthreads -m \$addmemory"M" -T "\${TMPDIR:-.}" -o '${output_bam}' |
There was a problem hiding this comment.
Please note that here the change improves things, but the entire pipe using multiple threads at each step seems questionable.
@bernt-matthias maybe you have an idea how to fix this properly?
There was a problem hiding this comment.
Are ampliconclip, collate and fixmate compute intense tasks that need a lot of memory / CPUs?
Maybe just remove the calls of collate, fixmate and sort completelty. It's not documented that these tools run anyway. If we would want to fix all problems that are potentially introduced by ampliconclip the docs suggest that we also should call calmd`... Let the user do this?
There was a problem hiding this comment.
Unfortunately, I still have never used the tool.
I agree with your points, but then lets do this separately. I will try to understand what's required next week and then open a new PR with those changes.
|
added the |
…ollection
Continuation of #3375
Fixes https://help.galaxyproject.org/t/samtools-fixmate-memory-allocation-error/17656