We're addressing issues with high replication datastore applications. In the future, however, this information is typically not enough. What are you doing? Are you making datastore calls? Are you doing URLFetch? Are you making XMPP or email API calls? Are CPU intensive tasks slower? This is important because there are a lot of operations for which 200ms would seem low latency. If you're trying to brute force SHA1 hashes and it's taking 500ms on average, you're doing okay.
One of the fortunate things about working with software developers instead of normal internet consumers is that I can usually just give the guidance, "report issues that way you want your users to report issues or bugs", and it gets the message across =). -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com On Wed, Mar 14, 2012 at 5:48 AM, andidol <[email protected]> wrote: > Hi, > > I have very high latency on my AppEngine since yesterday. It was really > fast before < 100ms. Now there are a lot of requests performing with > > 200ms without any reason. I did not update or did anything. > I'm using High Replication Datastore. > > Thanks > > -- > 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/-/UKDaOm5bNJsJ. > 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. > -- 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.
