-
Notifications
You must be signed in to change notification settings - Fork 6
CPU Limit Adjustments #1181
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
CPU Limit Adjustments #1181
Changes from 42 commits
f0d8cf0
e906b41
14c751d
293f63c
f7f72ec
94cfb76
509c717
1a65ecf
77ee45e
c9c70d6
7b8be53
bcd61cd
58e1030
ed8d479
dda6e01
f6f4f36
5dca5c3
4a653ef
3a21f0f
48fbbca
08c57db
5ecbfec
3ea41b5
29f2f2e
cdef57f
c0f393e
34a86fd
df3f5df
ac44663
4100b87
759f657
d60fd0c
a1e36c7
b856eb0
81ce9fb
0e32699
dc2846c
0840c61
b7c0dbc
1db1257
7726cff
5f95bb7
b0f962c
dede0a1
a7a9af9
4d2e914
1aa8e2e
a9d7b35
0086be0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -115,11 +115,12 @@ services: | |
| parallelism: 1 | ||
| placement: | ||
| constraints: | ||
| - node.labels.ops==true | ||
| - node.labels.gpu!=true | ||
| - node.labels.dynamicsidecar!=true | ||
|
||
| resources: | ||
| limits: | ||
| memory: 1G | ||
| cpus: '2' | ||
| cpus: '6' | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why this number? What is the reasoning behind? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the number of available CPUs are not taken into account, and afaik this is correct, they do not matter (as much). [talk to me for clarification ;)] The number is a guess based on prometheus observation on osparc-master (e.g. PromQL There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nevertheless @mrnicegyu11 if you set a limit above what is available in reality, the container never starts. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK then I vote for removing the limit alltogether. I can see that it was throttled >7 (additional) CPUs at a time on master, so 8 CPUs would be the right number. But this is too high to put into the section if what @sanderegg says is correct. @YuryHrytsuk @sanderegg There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Optional: Test CPU Limit |
||
| reservations: | ||
| memory: 128M | ||
| cpus: '0.1' | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -481,7 +481,7 @@ services: | |
| cpus: "0.1" | ||
| memory: "256M" | ||
| limits: | ||
| cpus: "0.5" | ||
| cpus: "1.0" | ||
| memory: "1G" | ||
|
|
||
| director-v2: | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chore:
.master.docker compose file or j2 instead of negative labelson all deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
optional: test / precommit (minor)