GAE pricing is multiplied by 3 for my usage !!!

[Stéphane Cohen]

Hi,

I have been using GAE since the beginning. One of my application is
very resource consuming and, with the introduction of ficed billing
for backends, I optimized it to use the full capacity of the 6
backends I am using.

The problem now is the Database : My app is performing a

[Stéphane Cohen]

Hi all,

The problem now is the Database : My app is performing a lot of writes/
reads that were not charged up to now and now ... Google is charging
more for the read/writes than for the 6 backends, including 1 b4 and 1
B2 !!

Results : The price of this app will switch to 400 USD to 1300 USD
(X3). Not normal.

Is there a way to optimize this the same way we optimize the usage of
backends?

Otherwise I fear we will have to move out of GAE.

Thanks and regards.

[Gerald Tan]

Optimizing writes: Indexes are probably what will make most apps pay through the nose. If you have properties that do not need to be searched or sorted, make sure they are unindexed.

Optimizing reads: Use memcache as much as possible. Also, keys-only queries are a lot cheaper (7x) than entity-fetch queries, so look for opportunities to use keys-only queries.

Look for opportunities to bundle several entities together and storing them serialized into one fat entity (bearing in mind the max entity size of 1MB). For large data that don't change a lot, you could even store them into the blobstore instead.