5 ms·
> For all other storage classes, Class A operations pricing in multi-regions and dual-regions will increase to be double the Class A operations pricing in regio
by twistedpair 5y ago
> For all other storage classes, Class A operations pricing in multi-regions and dual-regions will increase to be double the Class A operations pricing in regions.
This is the real impactful change. This is for ALL STORAGE CLASSES, not just Coldline. As someone who manages billions of objects in GCP, I know very well that each of those object write is a Class A operation, so 2x in price.
Also keep in mind that anyone storing objects durably (DR, anyone?), e.g. your customer data, is using multi-region, so this is a notable cost impact.
Note that there is a curious inflection point where, the Class A/B operations on an object cost _more_ than the (bytes) storage cost, depending how long you retain the data. That's where this is very impactful.
Annual multi-regional Standard _storage_ cost for a 19MiB object
e.g. 0.026 $/(GiBmo) 12 mo/yr * 19 MiB/yr = 5.95E-06 $/yr/obj
Annual multi-regional Standard storage cost for an object that you 1x write (A), and 2x read (B).
e.g. 0.05/1e4 $/A req + 2 * 0.004/1e4 $/ B req = 5.80E-06 $/yr/object
Here we see that the old annual "storage" carrying cost for this 19MiB object was less than the "request" cost. Now double the cost of the operations and you should consider storing fewer, bigger objects.
- thematrixturtle 5y agoAll data on GCS is stored durably (14 9s or something ridiculous like that). The only reason to use dual/multiregion is for lower latency, you're basically paying for geo replication. Of course, I'm sure many users are not aware of this, and it's not helped by the GCP console defaulting to multi when creating new buckets.
- GeneralMayhem 5y agoAlso for availability, if you need extremely high uptime - single-region outages are not unheard of, and even if your data is still there when they come back, you might have lost a significant amount of money and/or trust in the meantime.
- twistedpair 5y agoDurability is great, but availability is also crucial, unless your business can tolerate hours or more of availability outages. Let's say us-central1 is down for some reason (has happened a number of times), but your customer workloads need to keep running uninterrupted, so you fail over to us-west2. Where should your customer files, that need to be read/written for the customer workloads, be written then? If you kept them all in the region that's on the fritz, you've got upset customers, broken SLAs, etc.