Ah, that is pretty damn cool. No there wasn't an instance started, this is totally typical for an entire day of requests.
I've taken a screenshot, http://burtonini.com/temp/appstats.png Unsurprisingly the bulk of the time is spent in datastore_v3.Put(). So, first rookie question. Bar has a ReferenceProperty to Foo, I create and put a Foo and then create the Bars, finally putting the created Bars (and the original Foo, because that gets updated as the Bars are created) at once by passing a list of them to db.put(). Is it worth pre-allocating keys, or is this double-put not a concern? I then do some cleanup with a query and deleting some entities, but from the stats this isn't a problem at all. I've turned off indexing for a number of fields that I know I'll never index, and Bar is an entity child of Foo. If legal approve this project for own-time I can show you the source, but not at the moment. I'll risk the wrath of legal and show you my entirely trivial data model: class Session(db.Model): user = db.UserProperty() timestamp = db.DateTimeProperty(auto_now_add=True) machine = db.StringProperty(indexed=False) s_hash = db.IntegerProperty() class Window(db.Model): session = db.ReferenceProperty(Session, collection_name="windows", required=True) tabs = db.ListProperty(db.Link) Nothing stupid there, right? A typical 1-to-many relationship really. Thanks for the help, Ross -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
