Resource requests and limits about systemk HOT 5 OPEN

Here's the possible formats for Pod CPU resource requests and limits:

• an integer value, such as 2
• a fraction, such as 0.1
• an integer value in millis, such as 500m

All formats can be present in the same Pod spec and are directly translatable to milliseconds, which is supported by CPUQuotaPeriodSec, eg:

• 2 == 2.0 == 2000m
• 0.1 == 100m

Do you see any limitation of just going w/ that attribute?

from systemk.

from systemk.

Actually, I got it wrong when it comes to systemd primitives. CPUQuota is the field to use and it supports percentage alone. The conversion should be trivial, though.

Now, this only covers resource limits and not requests.

from systemk.

from systemk.

One problem I see is that it seems that enabling accounting for one slice means parent and child slices are affected too which may not be desirable.

from systemk.