Understanding scheduler savings behaviour over time

Prev Next

This article explains the savings behaviours you can expect to see after configuring a schedule in Cost Analyzer.

When you configure a schedule, expect the following behaviours:

  1. If you configure a schedule part way through the month, you will not see the full savings benefit for that first month.

  2. The month after the schedule is configured, you will see the biggest cost reduction.

  3. In subsequent months, the active schedule becomes the baseline. Costs stabilize at the lower level; you will not see a large drop every month.

The graph below shows a simplified example.

The graph lines are:

  • List price = The cost of resources at Azure list price, with no commitment discounts applied.

  • Potential savings = The amount you would save by applying the schedule, compared to list price with no schedule.

  • Amortized cost = The price you actually paid.

  • Monthly savings compared to last month = Expect a spike in month 2 as the schedule takes full effect. From month 3 onwards, savings remain consistent; there are no new savings beyond what was already achieved.

  • Cumulative savings = The total savings accumulated over time, compared to taking no action.

Sample Data Behind Graph

Month

List Price

Potential Savings

Amortized Cost

Monthly savings compared to last month

Cumulative Savings

1

932.4

545.22

932.4

0

0

2

932.4

545.22

545.22

387.18

545.22

3

932.4

545.22

545.22

0

1090.44

4

932.4

545.22

545.22

0

1635.66

5

932.4

545.22

545.22

0

2180.88

6

932.4

545.22

545.22

0

2726.1

7

932.4

545.22

545.22

0

3271.32

8

932.4

545.22

545.22

0

3816.54

9

932.4

545.22

545.22

0

4361.76

10

932.4

545.22

545.22

0

4906.98

11

932.4

545.22

545.22

0

5452.2

12

932.4

545.22

545.22

0

5997.42