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

Nextflow review @bobturneruk ep5 , CPUs, cores and threads #128

Open
ggrimes opened this issue Apr 23, 2024 · 1 comment
Open

Nextflow review @bobturneruk ep5 , CPUs, cores and threads #128

ggrimes opened this issue Apr 23, 2024 · 1 comment

Comments

@ggrimes
Copy link
Collaborator

ggrimes commented Apr 23, 2024

Is it worth making the difference between CPUs, cores and threads clear here? https://carpentries-incubator.github.io/workflows-nextflow/05-processes-part2.html#directives

@ggrimes
Copy link
Collaborator Author

ggrimes commented Apr 23, 2024

would adding this text from https://www.nextflow.io/docs/latest/process.html#cpus in a callout be sufficent?

The cpus directive allows you to define the number of CPU required by the process’ task. This directive is required for tasks that execute multi-process or multi-threaded commands/tools and it is meant to reserve enough CPUs when a pipeline task is executed through a cluster resource manager.

In the Glossary i could add

A core is a physical part of a CPU that can read and execute program instructions. Modern CPUs can have multiple cores, allowing them to perform multiple tasks simultaneously. When you specify the number of cores in Nextflow, you are typically talking about the same concept as CPUs in the cpus directive — physical cores unless the system treats hyperthreads as separate core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant