Hi Will, Here are a few of my thoughts and suggestions. The datastore will occasionally have spikes in latency / error rates, for reasons outside of your apps control. Your best bet for dealing with periods of increased latency is to optimize your requests. It sounds like you have a good handle on what your app is doing, but a little addition review never hurts -- use Appstats to profile your RPCs. Appstats is great for making sure no unexpected calls are being made and for identifying spots that need some optimization.
It also sounds like you might need to handle error's a little differently. Maybe you should catch those errors and defer writing the entity using the task-queue, if possible. And/Or return feedback to the client that the save failed; if the client is a browser at least let the user know the save failed so their data is not _unexpectedly_ missing. Also, what are your apps cold start times like? If your app takes a long time to bring up a new instance that could cause problems. There are several things you could try, such as minimizing start-up time imports. Robert On Mon, Nov 15, 2010 at 09:52, Will <vocalster....@gmail.com> wrote: > My site doesn't have too much traffic, but now and then I see this warning: > > Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving cluster is > under unexpectedly high or uneven load. If you see this message frequently, > please contact the App Engine team. > > Just half an hour ago, I saw one DeadlineExceededError and one > TransactionFailedError, immediately followed by 5 warnings mentioned above, > within roughly 30 seconds, when my application was trying to insert some > text data into datastore, in one plain put(). > > The load I saw for that particular url was about 13 requests per minute. > Well, this kind of load shouldn't cause datastore to choke in a way as I've > seen, in my expectation. > > This problem results in data loss in my app and then bad > customer-experiences. > > Should I expect this is the current capability of datastore/GAE? Or are > there any guidelines for minimizing this problem? > > My app id is 'qyingweb'. > > Thanks, > > Will > > -- > 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
