Fwd: Did App Engine update the datastore quota?

172 views
Skip to first unread message

Kamran (Google Cloud Support)

unread,
Jul 2, 2016, 1:55:29 PM7/2/16
to google-a...@googlegroups.com


On Saturday, July 2, 2016 at 1:04:16 PM UTC-4, Sunny Jerry wrote:
Hi

I've noticed that GAE's document said it will change the datastore quota at July 1st (https://cloud.google.com/appengine/pricing#costs-for-datastore-calls), makes it more clearly and easily to developer,.
But today when I try to delete 1000 keys in datastore, it still cost 64 percent of my datastore write operations, and all quota items in quota page seems not been updated as they said in documentation.

Any ideas?
Thanks 

troberti

unread,
Jul 2, 2016, 3:42:31 PM7/2/16
to Google App Engine
Seems that they did. Our reported datastore usage is 15% lower than before. Doesn't seem to offset the higher costs of writes for us though :/ 

Sunny Jerry

unread,
Jul 2, 2016, 11:55:25 PM7/2/16
to Google App Engine
But once you go to the quota details page (https://console.cloud.google.com/appengine/quotadetails)
You will find all quota item related with datastore still use the old quota now

Datastore Write Operations
0 of 0.05 Million Ops

Datastore Read Operations
0 of 0.05 Million Ops


Datastore Small Operations
0 of 0.05 Million Ops
Datastore Entity Deletes
0 of 0.02 Million Ops


All small operations should be unlimited and entity writes should be 0.02M, the deletion of an entity should not reflect on datastore write operations but now delete 1000 entity cost me 60% write operations. 

Sunny Jerry

unread,
Jul 4, 2016, 5:24:53 AM7/4/16
to Google App Engine
Friendly ping since nobody can answer my question

Dan McGrath

unread,
Jul 7, 2016, 11:06:07 AM7/7/16
to Google App Engine
There is a display issue for the new pricing changes we are working to resolve.

Regards,
Dan

Sunny Jerry

unread,
Jul 7, 2016, 8:52:06 PM7/7/16
to Google App Engine
Happy to know that, thanks~

Sunny Jerry

unread,
Aug 1, 2016, 4:31:54 AM8/1/16
to Google App Engine
Hi

Any timetable to fix this?

Thanks

On Thursday, July 7, 2016 at 11:06:07 PM UTC+8, Dan McGrath wrote:
Reply all
Reply to author
Forward
0 new messages