Howdy pardners, I have a busy (40 req/sec) app that is occasionally throwing Timeout errors on datastore operations. I'm not sure what the cause of these errors is - contention perhaps? - but in an effort to reduce the amount of data being written, I want to confirm my understanding of the put() operation.
Given the following model, class Listening(db.Model): listener = db.ReferenceProperty(User,collection_name="listening_to_set") listenee = db.ReferenceProperty(User,collection_name="being_listened_to_set") created_at = db.DateTimeProperty(auto_now_add=True) and assuming that no custom indexes have been defined, is it true that a put() operation will write the entity to three different places? (indexed on listener, indexed on listenee and indexed on created_at) I am in the habit of sprinkling non-essential "created_at" properties throughout my models, but I'm suspecting now that this carries significantly more burden on the GAE datastore relative to MySQL. Any insight? Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
