Re: High number of read operations

[khaled....@gmail.com]

Hello,

It depends on what operations you are doing, you mentioned "Everytime we save an operation it costs 8-10 reads". Did you mean write operations? In that case it should reflect on your write operations not read.

If you meant read operations, then it depends on how your data/entities are organized. Maybe you read from multiple entities? It can be clearer if you share the entities structure you are using.

For reference you can check the Best practices guide there might be something that can assist you,

On Wednesday, April 28, 2021 at 6:43:32 PM UTC+2 Elena Mata Yandiola wrote:

Hi,

Could you please tell me all the reasons that you may encounter for having many more read operations than expected in Datastore? E.g. Everytime we save a operation it costs us 8-10 reads and we don't know why. As we can't see the reading costs broken down in the billing part of the console (we can see the read costs, but we don't know why we have that nb. of reads), we have no clue what can be happening.

Hope you can help me,

Thank you,