Intelligent scaling documentation #326
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dgkanatsios
force-pushed
the
intelligentscaling
branch
3 times, most recently
from
ff35c32
to
9318e26
Compare
dgkanatsios
force-pushed
the
intelligentscaling
branch
from
9318e26
to
21808c4
Compare
javier-op
approved these changes
Jul 21, 2022
KalonJ-MSFT
approved these changes
Jul 21, 2022
cmd/standby-forecaster/main.go
Outdated
| @@ -167,7 +167,7 @@ func scaleGameServerBuild(ctx context.Context, totalServersNeeded int, config Co | |||
| if err != nil { | |||
| return time.Time{}, err | |||
| } | |||
| // To determin how many standby servers are needed by the forecase, we need to subtract the active servers | |||
| // To determine how many standby servers are needed by the forecase, we need to subtract the active servers | |||
There was a problem hiding this comment.
nit: forecast, not forecase
docs/howtos/intelligentscaling.md
Outdated
|
|
||
| Prediction is implemented using [linear regression](https://en.wikipedia.org/wiki/Linear_regression) and [Holt-Winters](https://en.wikipedia.org/wiki/Exponential_smoothing#Triple_exponential_smoothing_(Holt_Winters)) methods. The algorithm takes the top value and sets the `standingBy` accordingly. It is the user's responsibility to set the `max` in a proper value. | ||
|
|
||
| You can use the forecaster immediately with Thundernetes. Until it has 2 "seasons" worth of data, the holt-winters calculation will not work effectively, but the linear regression forecasters will work just fine. |
| |---------------|---------------|-------------| | ||
| | `maxValue` | `100` | Maximum value of the load. | | ||
| | `frequency` | `time.Hour` | ForecastFrequency of the load. | | ||
| | `jitter` | `0.15` | Jitter of the load. | |
There was a problem hiding this comment.
this might be clear to the general audience, in which case disregard, but we may want to specify under what circumstances jitter should be used for simulation values
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding docs about intelligent scaling, plus re-ordering the "How To's".