App Engine charges $6,500 to update a ListProperty on 14.1 million entities

Re:App Engine charges $6,500 to update a ListProperty on 14.... by cr4zy on Friday January 06, 2012 @12:29AM (#3432111)

Python 2.7 is experimental and requires migrating to the new datastore (high replication) which is a lot more expensive. So you might not want to do this if your costs are coming from datastore writes.

Also, high replication queries can return stale results unless you use ancestor queries. Ancestor queries require putting entities in groups by giving them all the same parent (which can never be changed). Basically it's a very inflexible semaphore and kind of sucks IMO.

Your suggestions in general are very good though. Thanks, I'm switching my DNS to CloudFlare now.

[ Parent | on HN ]

Re:App Engine charges $6,500 to update a ListProperty on 14.... by stickfigure on Friday January 06, 2012 @02:30AM (#3432413)

The HRD is the same price as the Master/Save datastore. In the old pricing regime it was more expensive, but now they are at parity.

It's true that eventual consistency of queries on the HRD can be tricky to program around. On the other hand... your data is replicated to 3+ datacenters and failed over in realtime. Pretty rad.

[ Parent | on HN ]

Re:App Engine charges $6,500 to update a ListProperty on 14.... by yahelc on Friday January 06, 2012 @09:19AM (#3433341)

Ah, yes. My unusual advantage here is that SharedCount doesn't use the datastore, which I now realize is likely not the case with ThatHigh.

(In fact, when I had to migrate my app from MS to HRD, it kept failing because I didn't have any datastore entities. The workaround was to just create a single entity)

[ Parent | on HN ]