My point is that no adjustment to the scheduler will ever really solve the problem. To the extent that it limits your bill, it does so by sacrificing user experience. Sure you might prevent a second instance from starting but that just means some poor sod is sitting around waiting for his browser to load.
The solution to this is multithreading. Hard stop. Jeff PS Fixed the colors... still getting used to tumblr. On Fri, Sep 9, 2011 at 6:29 PM, Steve <[email protected]> wrote: > Thanks for the good FAQ. I have to strenuously disagree though with calling > all the scheduler complaints a red herring. > It's legitimate complaint and mindbogglingly simple to fix by giving users a > control called Max-Instances instead of Max-Idle-Instances. Right now we > have to play all these stupid tuning games to keep the scheduler from > fanning things out in unsustainable ways. If we could just set a hard limit > we could make sure it never fanned out past a certain level of instance > parallelism. It's such a freaking easy thing to fix but Google doesn't want > to do that for whatever internal reason. > Sigh... > > -- > 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/-/9YEEiFuJsRUJ. > 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.
