Hi Ryan, Thanks for your explanation!
Actually, upon further analysis my write timeout rate is more like 1-3% and timeouts happen every 5 - 10 minutes throughout the day. Although I have retry logic to deal with this, I feel uneasy with so many errors in my logs. It doesn't sound like you think that indexing a 10-valued list is a big contributor to the timeouts, so I'll leave it alone. Do you have any other ideas that could reduce the timeout rate? So I gather the best way to replace a property in App Engine, is actually to leave the old property in the model spec but just not write anything to it in the future, to avoid exceptions, right? Alex On Tue, Sep 30, 2008 at 1:06 PM, ryan <[EMAIL PROTECTED]> wrote: > > hi alex! serializing the list property into json shouldn't make much > of a difference in the timeout rate, but you're welcome to try it. > honestly, though, .01% is noticeable, but i wouldn't exactly call it > "large." regardless of how your data is shaped, you'll at least see a > small timeout rate. .01% is in the ballpark. > > as for deleting a property in your model definition, that's backward > compatible. the existing data in the datastore will remain unchanged. > when you load entities with the new model definition, they'll just > ignore the old property, and not populate it in new entities. other > changes, e.g. changing a property type or adding a required property, > will cause exceptions when you fetch entities created with the old > model definition. you can use Expando and optional properties to help > with schema changes like these. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
