You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pipeline has a massive disk footprint (approx. 1.5 TB per Gbp of sequence) that is mostly caused by each step storing its output file, e.g. in the samtools sub-workflows.
We can often combine consecutive steps with by piping the output of one step into the next one, thus removing the need to write a (often large) file on disk. This not only reduces the disk footprint, it can also make the pipeline much faster, especially when the filesystem is being heavily used.
The text was updated successfully, but these errors were encountered:
Description of feature
The pipeline has a massive disk footprint (approx. 1.5 TB per Gbp of sequence) that is mostly caused by each step storing its output file, e.g. in the samtools sub-workflows.
We can often combine consecutive steps with by piping the output of one step into the next one, thus removing the need to write a (often large) file on disk. This not only reduces the disk footprint, it can also make the pipeline much faster, especially when the filesystem is being heavily used.
The text was updated successfully, but these errors were encountered: