You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.
For a particular config, or comparing two configs, what are the expected effects in terms of costs.
Should be seen in relationship with #45 (analyzing perf on real data).
Also interesting for evaluating code changes, like #33.
The text was updated successfully, but these errors were encountered:
Maybe the default usage could be to to show estimated cost, compared with the currently active config? At the end should just be the grand total, with +- difference (and %). There should also be a similar breakdown per-role, so one can evaluate where differences come from.
Significant differences should possibly be highlighted with a warning color yellow/orange.
When storing scaling config in git, one can use git show to get alternative versions: git show HEAD~4:autoscale.guv.yaml
For a particular config, or comparing two configs, what are the expected effects in terms of costs.
Should be seen in relationship with #45 (analyzing perf on real data).
Also interesting for evaluating code changes, like #33.
The text was updated successfully, but these errors were encountered: