Thanks Kenneth! Its been a busy day so I haven't been able to answer all the questions in the group, but I will do so tomorrow morning (well, morning my time) as well as cull for the questions that seemed concerning and people wanted answered.
I'll make sure to include all of these, but for now, some answers below: On Thu, May 12, 2011 at 12:14 AM, Kenneth <[email protected]>wrote: > Greg mentioned he was putting together an FAQ so let's help him out! > > If you're going to answer this just put in your question into a single > line, let's not try and answer them here or give opinions, there's plenty of > other threads for that. I do understand that Google doesn't have answers to > some these. > > Here's my list: > > 1) What is the time granularity of the instance pricing? ie if I have an > instance up for 5 minutes, what am I charged, $0.08 / 60*5? > The smallest granularity will be 15 minutes, but part of the scheduler change is to ensure we don't start instances to serve 1 request. > 2) Will I be able to tune the scheduler myself, ie set it to performance or > low cost, Will I be able to limit the min or max number of instances > created (with the obvious impact on user experience)? > Yes, you will be able to tune the scheduler, specific controls are still being worked on, all of the ones you mentioned seem like reasonable ones. > 3) Python concurrency, will this require any code changes, do you have any > estimates based on your testing of the number of well behaved requests per > second a single instance will be able to handle for a given framework? > We are still evaluating various methods to potentially handle Python concurrency, so don't yet have an answer to whether it will require code changes. In terms of the number of requests per second that can be handled depends primarily on your code. We've done stats on what the max requests that can be handled and I'll post those numbers. > 4) Database charges, when can you give us more details over what Max gave > in the other thread, are you charging for deletes, what do you expect the > ratio to be between the new pricing metric and the Datastore API calls > metric we have today? > Soon. :) > 5) Will you be charging differently for instances that use different > amounts of memory, since this seems to be the cost that you're going after > that isn't charged for in the current model. > The current plan is that all frontend instances have the same CPU and memory limits but there is the potential to later allow customers to configure the instance size for frontends. I'll gather all of these into a document tomorrow. Thanks, Greg > > Thanks, > Kenneth > > -- > 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.
