I've adjusted the Requests / Limits of portal pods according to real
usage of "Orange Openlab" and "Onap daily master".
Calculation is the following:
per deployment:
* CPU/Mem requests is max of average from the two deployments
* CPU/Mem limits is (max of max from the two deployments) * 1.2
Moved portal-widget CPU limit to 1 as it's not starting if set to lower
than that.
Full values are available on jira ticket
(https://jira.onap.org/browse/PORTAL-517).
Change-Id: Ic02fef386e05351a6fa9e47bf47d5c2046f490e3
Issue-ID: PORTAL-517
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Signed-off-by: Lorraine Welch <lb2391@att.com>
resources:
small:
limits:
- cpu: 2
- memory: 10Gi
+ cpu: 2.2
+ memory: 800Mi
requests:
- cpu: 1
- memory: 6Gi
+ cpu: 30m
+ memory: 460Mi
large:
limits:
cpu: 4
resources:
small:
limits:
- cpu: 2
- memory: 8Gi
+ cpu: 500m
+ memory: 3.75Gi
requests:
- cpu: 1
- memory: 4Gi
+ cpu: 160m
+ memory: 2.8Gi
large:
limits:
cpu: 4
resources:
small:
limits:
- cpu: 800m
- memory: 1Gi
+ cpu: 460m
+ memory: 175Mi
requests:
- cpu: 400m
- memory: 500Mi
+ cpu: 10m
+ memory: 100Mi
large:
limits:
cpu: 2
resources:
small:
limits:
- cpu: 4
- memory: 10Gi
+ cpu: 600m
+ memory: 1.6Gi
requests:
- cpu: 2
- memory: 5Gi
+ cpu: 10m
+ memory: 1.3Gi
large:
limits:
cpu: 8
small:
limits:
cpu: 1
- memory: 4Gi
+ memory: 430Mi
requests:
- cpu: 500m
- memory: 2Gi
+ cpu: 1m
+ memory: 360Mi
large:
limits:
cpu: 2
resources:
small:
limits:
- cpu: 500m
- memory: 600Mi
+ cpu: 100m
+ memory: 200Mi
requests:
- cpu: 250m
- memory: 300Mi
+ cpu: 1m
+ memory: 80Mi
large:
limits:
cpu: 1