You cannot just compare GAE with Rackspace simply because GAE is unmanaged,
we don't do a thing.

Though I would still maintain that the prices are indeed high.

On 12 May 2011 21:46, Peter Petrov <[email protected]> wrote:

> My single question for Greg's FAQ:
>
> 1) What is the justification behind the extremely high price for additional
> instances?
>
> Here is a comparison between a GAE Frontend Python Instance and a small
> Rackspace Cloud Server:
>
> GAE Frontend Python Instance:
> -------------------------------------------------
> Monthly price: $57.60 ($36.00 if reserved)
> RAM: 128 MB memory cap
> CPU: 600 MHz limit
> Capabilities: Limited by the Python sandbox. No native code execution.
> Single-threaded right now, possible future multi-threading obstructed by the
> GIL.
>
> Rackspace Cloud Server 256 MB:
> -------------------------------------------------
> Monthly price: $10.80
> RAM: 256 MB fixed
> CPU: Guaranteed proportional minimum; Free CPU bursting (I'm using the full
> power of 4 cores 99% of the time)
> Capabilities: Full-featured Linux box, can do whatever you want on it.
>
>
> On Thu, May 12, 2011 at 10: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?
>> 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)?
>> 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?
>> 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?
>> 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.
>>
>> 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.
>



-- 
-Nischal
+91-9920240474
twitter: NischalShetty <http://twitter.com/nischalshetty>
facebook: Nischal <http://facebook.com/nischal>

<http://www.justunfollow.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.

Reply via email to