eggnog_proteins.dmnd needed for tmpfs #458
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Placing eggnog db in memory is unbeliveably fast for the annotations step. 👍
The
eggnog_proteins.dmnd
seems also to be included. I need this for our clusters, also eggnogdb/eggnog-mapper#277 (comment)A flaw for putting the eggnog db in memory:
The
cp
will cause crashes if two/moreqsub
jobs run in the same computing node. In this case, the jobs use the same/dev/shm
, and thecp
(except in the first job) will collapse if the files are already there.It's a bit tricky to solve it. You can't re-write the db file, if one job's using it. Also, the jobs in one node/cluster didn't finish in the same time.
Maybe just leave it as it is. At least, it's easily controlled to place annotation rule in separate nodes if we choose approriate number of threads. Or repeat the pipeline several times.