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

Properly limit CPU shares in sandbox #35

Closed
mejedi opened this issue Feb 23, 2020 · 2 comments
Closed

Properly limit CPU shares in sandbox #35

mejedi opened this issue Feb 23, 2020 · 2 comments

Comments

@mejedi
Copy link
Collaborator

mejedi commented Feb 23, 2020 •
edited
Loading

Currently not done; all runners have just 1 CPU, so only one job runs at a time. Required for arm64 support (#33), the most likely Cloud provider Scaleaway offers 4 CPU instances.
@mejedi
Copy link
Collaborator Author

mejedi commented Oct 4, 2022

Scaleway doesn't offer Arm instances anymore. This is still important though as the submitted code can fork multiple processes which will compete with the server for CPU time.

Fly.io doesn't currently support cgroup2, and I'd rather not build something for obsolete cgroup v1.

As multiprocessing is not particularly important, prevent fork with seccomp as the band aid.

@mejedi
Copy link
Collaborator Author

mejedi commented Oct 8, 2022

Fixed as of v1.2.1

@mejedi mejedi closed this as completed Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mejedi