diff --git a/source/user_guide/helm_settings.rst b/source/user_guide/helm_settings.rst index ecd53402567fe74e9098f6dd1aa4486e8eeac2c2..5be39fdfcdb977a2be1afbd0ec4d4e7e42f78d7f 100644 --- a/source/user_guide/helm_settings.rst +++ b/source/user_guide/helm_settings.rst @@ -158,20 +158,20 @@ instance going down with a wrong commit, or a slowed down as you started multiple computation on it. In you production environement you will have only one branch, the ``main`` -branch. But in production using nodowntime is adviced, and autoscaling +branch. But in production using nodowntime is arguable, and autoscaling could also be a good idea if you may face peek of usage by numerous users. Also dedicating more CPU and RAM to your app can make sens. By re-using previous example, but after adapting settings after the previous discussion, we then have a quota needs of: -+------+--------------+-------------+-------------+----------+------------+--------------------+ -| | Memory limit | Autoscaling | No downtime | Branches | Multiplier | Quota memory limit | -+======+==============+=============+=============+==========+============+====================+ -| Dev | 2Gi | 1 | no | 3 | =3 | 6Gi | -+------+--------------+-------------+-------------+----------+------------+--------------------+ -| Prod | 4Gi | 3 | yes | 1 | =4 | 16Gi | -+------+--------------+-------------+-------------+----------+------------+--------------------+ ++------+------------------------+-------------+-------------+----------+------------+--------------------+ +| | Container memory limit | Autoscaling | No downtime | Branches | Multiplier | Quota memory limit | ++======+========================+=============+=============+==========+============+====================+ +| Dev | 2Gi | 1 | no | 3 | =3 | 6Gi | ++------+------------------------+-------------+-------------+----------+------------+--------------------+ +| Prod | 4Gi | 3 | yes | 1 | =4 | 16Gi | ++------+------------------------+-------------+-------------+----------+------------+--------------------+