Hi Eric, You are right Eric, some of the values are too high and some of the ranges between small and large are not ideal. We are working right now to reduce some that we know are concerning.
Great effort has been made to reach out and get accurate values for each component from the project teams. For those that were able to help direct the OOM team, we believe we have a good starting point for minimum and maximum limits. But any and all values are up for discussion and can be changed. For those teams that were unable to provide us with data, a best effort approach was taken. The OOM team are not experts in the components themselves. But it seems you have some valuable insight into what some of the limits should be based on your recent efforts to reduce the onap footprint in other areas. ☺ I would like to setup a meeting with you to discuss some of your findings and see how we can work together to come up with some guidelines to assist the project teams in this area. If that works for you please let me know and we can arrange a date and time? Thanks, Mike. From: <[email protected]> on behalf of Eric Debeau <[email protected]> Reply-To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Date: Wednesday, September 19, 2018 at 4:18 PM To: "[email protected]" <[email protected]> Subject: [onap-discuss] Memory and CPU limits for containers #oom Hello When deploying the master branch, I noticed that most of components have now defined resources requirements in helm charts for 2 configurations: small and large. That is good to avoid containers to consume all the memory. But, I believe that the minimum values set are very high for a small deployment and will have a bad effect on the minimum footprint and for basic test purposes. For example, some mariadb containers are set with a minimal 4 Gi memory for small configuration (eg NBI, SO) while it should be possible to start with 0.5 Gi (eg Policy) and probably less (like Clamp with 0.2 Gi) while VID is set to 1Gi and Portal has not yet defined such values. We should define common rules for such components. I could not find any definition about the small and large configuration. It should be great to share it. We should also try to get the minimal memory and CPU consumption for the small configuration. Best Regards Eric This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12536): https://lists.onap.org/g/onap-discuss/message/12536 Mute This Topic: https://lists.onap.org/mt/25759200/21656 Mute #oom: https://lists.onap.org/mk?hashtag=oom&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
