On Thursday, July 19, 2012 12:55:15 AM UTC+2, hyperflame wrote:
>
>
> Even if you (hypothetically) built a datacenter with 100,000 machines 
> solely dedicated to hosting a single request queue, that datacenter 
> can still go down (earthquake, power, hurricane, etc). Far better to 
> simply dump requests into instance level queues and be done with it. 
>

That's fine, but all we're asking for is "don't dump those requests into an 
instance that isn't able to serve the request immediately".  If there are 
three instances running and one being started up, don't consider the latter 
in the population of instances to send requests to. Dump it into an 
instance level queue that is already running. Everything else remains 
constant.

I stand to be corrected, but I doubt that Google searches are dumped onto 
cold instances. They and Amazon conducted the research on how delay time 
affects user behaviour. If Brandon's unique searches make Google slow, 
that's a separate issue from instances waking up.  And I doubt Google slows 
down too much on long-tail queries. I just searched on "Just to be clear, I 
am agreeing with you in that the GAE scheduler" and it took: 1 result (0.21 
seconds)

-- 
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/-/tWpV1dLcwa0J.
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.

Reply via email to