-
Notifications
You must be signed in to change notification settings - Fork 115
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
Increase the default maximum number of tasks for balenaEngine #1844
Comments
[mbalamat] This issue has attached support thread https://jel.ly.fish/#/7b3aaf9b-fc3b-48f0-b63e-78931732a11a |
For reference, the number of maximum threads spawned by a service unit can be tested by running the following C program from an application container.
For example using the following Dockerfile:
Unfortunately BalenaEngine also creates transient systemd units using the d-bus systemd API. For the maximum number of threads to be lifted, they also need to remove the limit by doing:
Unfortunately instrospecting the systemd dbus it does not seem possible to set this property programmatically. I have yet to find a solution to do this without using the global DefaultTasksMax variable. |
Note that #1824 already sets:
|
@alexgg the commit that changes the service file was something I added to be closer to upstream, it's marked |
[robertgzr] This issue has attached support thread https://jel.ly.fish/e5391b02-bceb-4f8d-994d-bd912b2ae9d7 |
maybe we can use runc annotations to set the required property: https://github.com/opencontainers/runc/blob/master/docs/systemd-properties.md The problem is that there seems to be no good way to set those from docker. We would have to run an oci-hook and modify the runc |
[saintaardvark] This issue has attached support thread https://jel.ly.fish/b23a8cc0-c4fb-45b0-924c-15b8483cad7e |
Is this issue actively been worked on? I keep hitting the limit around 4900 threads... |
@robertgzr did you get to running a proof-of-concept with runc's |
[alexgg] This issue has attached support thread https://jel.ly.fish/15b7c512-1c30-4a0e-9101-33a9bbb44913 |
[alexgg] This issue has attached support thread https://jel.ly.fish/cdfeb30b-114f-45cd-a685-94d00fb9e9bf |
BalenaOS uses the default systemd maximum number of tasks per unit which is 15% of the maximum number of tasks in the system, which currently is around 4915.
This is deemed to be sensible, except in the case it is inherited by balenaEngine and limits the number of tasks in a container application.
This issue will remove the limit for the balenaEngine unit.
The text was updated successfully, but these errors were encountered: