Google Datastore新的定价效果操作 [英] Google Datastore new pricing effect operations

问题描述

Google数据存储将于7月1日起生效（ https://cloud.google.com/数据存储/文档/定价），并且我无法理解这些更改会对我产生什么影响。

我的KIND的确有一个结构。我的种类称为 MESSAGES ，它对于每个实体都是这样的：

  ID 
 FROM 
 TO 
 MESSAGE 
 DATE_CREATED 
 MISC1 
 MISC2 
  

我有一个关于 ID ， FROM ， TO ， DATE_CREATED ， MISC1 和 MISC2 。随着新的定价：

• 将新实体插入此类的成本是多少？




• 如果我运行查询来获取所有属性并返回10个实体，那么查询的成本是多少？




• 如果我运行投影查询以获取除MISC1和MISC2以外的所有属性，并返回10个实体，那么查询的成本是多少？

我更新了一个包含所有这些索引的实体会花费多少钱？


旧的定价主要基于多少你有的指数，但似乎新的价格并不是根据指数。关于理解读写成本的所有文档都以索引形式显示，因此如何在定价模型中应用没有索引的混淆令人困惑。我想知道这4种类型的操作在读/写/小操作方面会花多少钱。
写一个新实体



在当前的定价模型中，插入一个新实体需要为每个索引的实体+ 2个写入操作花费2个写入操作。





因此，在您的示例中，具有6个索引属性：





• 2 + 2 * 6 = 8写入操作


• 每10万个实体的实际价格为（8 * $ 0.06）
  
• 汇总当前价值：$ 0.48 / 100K






新的定价只需计入所写实体：




立即查询
$ b $ b

在当前模型中，您需要支付返回的实体数+ 1





• 11个读取操作@ $ 0.06 / 100K






在新的定价中模型，你只需要向数字实体收费





• 10实体阅读@ $ 0.06 / 100K






投影查询





阅读预测被视为小型行动并且是免费的。查询本身花费1次读取 - 这在当前和新的定价模型中保持不变。





更新实体



<在当前的定价模型中，更新一个新实体花费了1个写操作，每个索引实体+4个写操作。



所以在你的例子中，有6个索引属性这将是：





• 1 + 4 * 6 = 25个写入操作


• 每10万个实体编写（25 * 0.06美元）


• 当前总结：$ 1.50 / 100K






新的定价只需计入实体：





• 总结新：$ 0.18 / 100K





Google Datastore will have new pricing effective July 1st (https://cloud.google.com/datastore/docs/pricing) and I having trouble understanding how the changes will effect me.

My KIND does have a structure to it. My kind is called MESSAGES and it looks like this for the every entity:

ID
FROM
TO
MESSAGE
DATE_CREATED
MISC1
MISC2

I have an index on ID, FROM, TO, DATE_CREATED, MISC1, and MISC2. With the new pricing:

• What will be the cost of inserting a new entity into this kind?

• If I run a query to get all the attributes and it returns 10 entities what is the cost of the query?

• If I run a projection query to get all the attributes except MISC1 and MISC2 and it returns 10 entities what is the cost of the query?

• If I update a entity with all these indexes what will be the cost?

The old pricing is based primarily on how many index you have, but it seems the new prices are not based on indexes at all. All the documentation on understanding the costs of read and writes are shown with indexes, so it is confusing how it applies without indexes in the pricing model. I would like know how much these 4 types of operations would cost in terms of read/write/small ops.

解决方案

Writing a new Entity

In the current pricing model, inserting a new entity costs 2 write operations for the entity + 2 write operations per index.

So in your example, with 6 indexes properties it would be:

• 2 + 2 * 6 = 8 write operations
• The effective price would be (8 * $0.06) per 100K entities written
• Summary current: $0.48/100K

The new pricing just counts the entities written:

• Summary new: $0.18/100K

Regular Queries

In the current model you are charged the number of entities returned + 1

• 11 read operations @ $0.06/100K

In the new pricing model, you only get charged the number entities

• 10 entity reads @ $0.06/100K

Projection Queries

Reading projections count as 'Small Ops' and are free. The query itself costs 1 read though - this stays the same in both current and new pricing models.

Updating Entities

In the current pricing model, updating an new entity costs 1 write operation for the entity + 4 write operations per index.

So in your example, with 6 indexes properties it would be:

• 1 + 4 * 6 = 25 write operations
• The effective price would be (25 * $0.06) per 100K entities written
• Summary current: $1.50/100K

The new pricing just counts the entities written:

• Summary new: $0.18/100K

这篇关于Google Datastore新的定价效果操作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！