Yeah definitely but tbh a one-off expense at that scale while unfortunate isn't really lethal.
And tbh if you are performing ops at a scale where that level of expense is present it's nobody's fault but your own if your orchestration is cronjobs on the 58th second of the 59th minute of the last hour of the year.
And at any time scale past the order of seconds, this is a small enough time jump that it's a rounding error in ops expenses.
Comments
Yeah definitely but tbh a one-off expense at that scale while unfortunate isn't really lethal.
And tbh if you are performing ops at a scale where that level of expense is present it's nobody's fault but your own if your orchestration is cronjobs on the 58th second of the 59th minute of the last hour of the year.
And at any time scale past the order of seconds, this is a small enough time jump that it's a rounding error in ops expenses.