The scheduler is Google's way of protecting their own resources. Why would they allow anyone else to have control over how their resources are managed?
This suggestion doesn't make any sense from a business perspective. And you opened a feature request for this? No wonder the App Engine guys are so slow to complete new features. They have to waste time on this kind of unrealistic nonsense. On Sun, Sep 4, 2011 at 11:42 AM, Sergey Schetinin <mal...@gmail.com> wrote: > Seeing how scheduler has some problems and everyone's bill depends on > how well it does its job, I think it would be fair and would do a > great deal to make new costs more transparent if you open-sourced the > scheduler. Ideally, one would be able to override scheduler logic for > their application, but I don't think it will happen just because the > scheduler is most likely written in C (and for other reasons). So at > least seeing how the decisions to spin up and shut down instances are > actually made, we could have a constructive discussion about it. > > Please respond if you would like to see this happen too. > > -Sergey > > -- > http://self.maluke.com/ > > -- > 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-appengine@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-appengine@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.
