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.

Sign up for GitHub

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

Jump to bottom

👌 IMPROVE: Clarify use case of direct scheduler #400

Open
mbercx opened this issue Jul 28, 2021 · 0 comments
Open

👌 IMPROVE: Clarify use case of direct scheduler #400

mbercx opened this issue Jul 28, 2021 · 0 comments
Labels
priority/nice-to-have Nice improvement, but no biggie section/running-calculations Sections on running calculations and workflows type/improve Improving already existing content

Comments

@mbercx
Copy link
Member

mbercx commented Jul 28, 2021

The direct scheduler is used for the tutorial because we are typically only running a few calculations, so the resources of the machine are not overwhelmed.

However, if this is used in a production environment, the CPU and RAM will be fully used at some point, causing all sorts of issues. Hence, we should clearly state that the direct scheduler should not be used for running calculations to such an extent that they can overwhelm the resources of the machine.
@mbercx mbercx added type/improve Improving already existing content section/running-calculations Sections on running calculations and workflows priority/nice-to-have Nice improvement, but no biggie labels Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/nice-to-have Nice improvement, but no biggie section/running-calculations Sections on running calculations and workflows type/improve Improving already existing content
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mbercx