Update parameters-for-a-dynamic-scaling-policy-c966417.md #15
Conversation
| @@ -396,7 +396,11 @@ none | |||
| </td> | |||
| <td valign="top"> | |||
|
|
|||
| The minimum duration between two successive scaling triggers. After the first scaling trigger, the second trigger occurs after the specified interval. This duration enables the application to be stable enough before it starts the next trigger. For production environments, a longer duration is recommended. | |||
| After this scaling triggered, the next scaling trigger happens after the specified interval. | |||
There was a problem hiding this comment.
After the scaling has been initieated, the next scaling action happends at the earliest after the specified internval
There was a problem hiding this comment.
"The period following a successful scaling initiation during which no additional scalings can be initiated. This duration allows the application sufficient time to distribute workloads across all available instances before new scalings may happen. For production environments, a longer duration is recommended to ensure stability."
WDYT?
There was a problem hiding this comment.
Looks good but it increases cognitive overhead to read :)
I combine your suggestions in the following version:
"
The minimum duration between two successive scaling actions.
After this scaling has been initiated, the next scaling action can only occur after this specified interval. During this interval, no other scaling action can be initiated.
This interval ensures the application remains stable before initiating another scaling action. For production environments, it is recommended to set a longer interval.
"
asalan316
force-pushed
the
asalan316-patch-1
branch
2 times, most recently
from
eeaded8 to
46a4f59
Compare
Update cool_down_sec docs for better readibility Update parameters-for-a-dynamic-scaling-policy-c966417.md improve cool_down_secs
asalan316
force-pushed
the
asalan316-patch-1
branch
from
46a4f59 to
0a7bacb
Compare
Updated cool_down_sec docs for better readability