our app is seeing this problem too. we are on the master/slave datastore. I think it's unacceptable to allow master/slave to perform this poorly; I hope the app engine team will still fully support issues with the master/slave. I know migrating to the HR datastore is the right thing to do, but allowing the performance of the master/slave to suffer this badly is not the right way to motivate us to migrate...
There didn't used to be this many issues with the master / slave, so it seems as though the app engine team is scaling back support for the master / slave with the excuse that the better HR alternative exists. But what about those of us who have run our app on GAE for years? Migrating is a big deal, and we'd like to at least wait for the blobstore migration tool to be ready. In the meantime, I see no reason why the master / slave can't continue to perform reliably even if it has planned downtime and other understandable drawbacks compared with the HR. -- 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/-/J7vAk0U3EgQJ. 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.
