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. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/yuSHSwxaJdQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
