On Thu, Jun 2, 2011 at 6:24 PM, Sergey Schetinin <[email protected]> wrote:
> Greg D wrote a while ago: > > I know I haven't been responding in this thread a lot but I've been > reading what everyone is saying and working with the team here to map out > some of the details in light of this. I'll post next week with another > update on the additional aspects that are finalized enough to discuss. > > So two weeks have passed, can we get an update finally? > > -Sergey > > I'm guessing the appengine team wants to push out the new scheduler and compare old to new prices before getting into this discussion again. ~Vinuth. On 18 May 2011 23:06, Sergey Schetinin <[email protected]> wrote: > > A couple more questions for the FAQ: > > > > 1) What are the expected limits on the concurrency for Python 2.7 > > instances? Assuming the requests handlers / threads are just waiting > > for RPC to finish (say on urlfetch service), how many per-process are > > allowed? This is probably still TBD, but a ballpark figure would be > > very welcome. > > > > 2) How the keys-only queries will be charged for? > > > > 3) What controls are in place to make sure that the instances do not > > get stuck on a bad / slow host? I have experienced very different > > response times from a noop WSGI app hosted on GAE, and given the costs > > will now be tied very directly to the latency, how can you make us > > comfortable with the fact that this latency is volatile and often > > completely out of our control? (or remove the volatility) > > > > 4) Can we have some assurance that the hosts are not oversold and the > > CPU / Memory quota is actually guaranteed? Volatility in response > > times (as measured by the GAE dashboard itself) suggests that > > different hosts are under a different load and sometimes the > > instance's process has to wait to get to run on a CPU. (When a no-op > > app sometimes runs in 10ms and sometimes in 300ms+, that doesn't look > > like guaranteed CPU to me). > > > > 5) Can we configure scheduler to shut instances down faster than in 15 > > minutes? (And not get charged for that idle time). If not, please > > justify this limitation. > > > > 6) Will we have a way to explicitly shut down an instance from the > > instance itself? (Without returning an error, basically to suggest to > > scheduler that "this is the last request I want to handle") > > > > 7) Will the pricing become stable after this change? How can you > > assure us that it will? > > > > 8) Is there any intention to adjust the prices in a year or two to > > account for falling hardware prices? > > > > Thank you. > > > > -Sergey > > > > PS I also wanted to mention to people asking if GIL will be removed -- > > of course it will stay. Also, there's no need to remove it, so please > > don't make random requests and learn what GIL is and why it's there. I > > would bet that the concurrency will be via regular Python threads (no > > multiprocessing), but the app itself would not be allowed to spawn or > > control those threads. > > > -- > 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 [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.
