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

Reduce core usage in hello-config #469

Merged
merged 2 commits into from
Nov 20, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions docs/hello_nextflow/06_hello_config.md
Original file line number Diff line number Diff line change
Expand Up @@ -742,7 +742,7 @@ The syntax looks like this when it's by itself in a process block:
```groovy title="Syntax"
process {
withName: 'GATK_JOINTGENOTYPING' {
cpus = 8
cpus = 4
}
}
```
Expand All @@ -756,7 +756,7 @@ process {
memory = 2.GB
// allocations for a specific process
withName: 'GATK_JOINTGENOTYPING' {
cpus = 8
cpus = 4
}
}
```
Expand All @@ -774,8 +774,7 @@ nextflow run main.nf -profile my_laptop -with-report report-config-2.html

Once again, you probably won't notice a substantial difference in runtime, because this is such a small workload and the tools spend more time in ancillary tasks than in performing the 'real' work.

However, the second report shows that our resource utilization is more balanced now, and the runtime of the `GATK_JOINTGENOTYPING` process has been cut in half.
We probably didn't need to go all the way to 8 CPUs, but since there's only one call to that process, it's not a huge drain.
However, the second report shows that our resource utilization is more balanced now.

<!-- **TODO: screenshots?** -->

Expand Down
Loading