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
The cloud costs are the only recurring costs that vary significantly, so they should be worked out separately from other recurring costs as they require future planning.
The text was updated successfully, but these errors were encountered:
Need to add Azure costs too, Azure is used at the moment for Translation services for community.osm.org
Current costs are expected to be £26 per month. Cost will increase as adoption of community.osm.org site grows.
Costs consist of a predictable baseline with spikes for one-off batch operations. These batch operations might tasks like back-populating log tables, copying new files to S3, or ad-hoc of tile logs.
Tile log retention and aggregation #698 is not yet done - this should reduce our long-term costs as we will retain less data, but will shift some costs around in unknown ways.
For some reason, we've been getting credits since Oct 1st equal to our spend. We haven't had any bills to pay since the September bill which came in on October 2nd. This is excluding the render account. Because I don't know the source of this, I'm excluding these credits from the cost analysis.
Part of our S3 usage is backups, which we do not access on a regular basis. If we ever needed them, we would have significant bandwidth costs to download them.
Given all of these constraints, I fit the weekly data to a curve and got a cost of 26100 USD. This matches what I get for monthly data. If I used a linear fit to the last three months, I got 21k USD.
The cloud costs are the only recurring costs that vary significantly, so they should be worked out separately from other recurring costs as they require future planning.
The text was updated successfully, but these errors were encountered: