I've experienced the same. My app usually gets 20 - 50 requests per second.
Since few days ago it has started to get spikes hitting up to ~150 requests
per second. I don't see anything unusual in the logs. The load to my app
should be quite constant, nothing like the graph shows. From the graph
Yeah, I removed my post after 2 mins when I tested the API and realized that
it returned null every time. You were faster :)
--
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.co
How about using http://www.google.com/jsapi and
google.loader.ClientLocation.address.city
on the client side?
--
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
The 15 minutes start-up fee seems odd with the current scheduler. A Java app
with very low latency and high QPS would be billed a lot more than it should
be. That is because for some unknown reason GAE kills an instance when it
has reached exactly 9000 requests. I've tested this with several app
I hope if it's 0.5 hours (maybe I read 15 minutes in some doc?) then we'll
be able to "reuse" the billed amount for other instances created during that
time. I see it quite often that a new instance is being created and few
minutes later it goes away and few minutes later another instance is bei
