3 ms·
I was able to get my GAE costs way down by focusing on minimizing DB writes. Some tips: - Instead of storing an array in the database directly, store it as a j
by sarah2079 13y ago
I was able to get my GAE costs way down by focusing on minimizing DB writes. Some tips:
- Instead of storing an array in the database directly, store it as a json string. storing an array uses a DB write for every array element.
- Don't index things if you can get away with it (indexing doubles writes).
In my case I was using about 600 writes for every user action when I only needed two. This may be common knowledge, but I was pretty surprised that storing arrays was costing me so much.
- dougk7 13y agoI minimise costs by using a mix of GAE and AWS: Host the main application on GAE but for background services use AWS. E.g I use AWS SES for mails and S3 for storing uploads and blobs. Also storing objects that don't need indexes as pickled blobs in a parent model helps a lot. The advantage over JSON is that you don't need extra code to parse, (de)serialized and validate the object.