Another good proposal was charging based on total time taken to serve the request. Given that there is only one type of Frontend instance, where RAM and CPU are constant for all instances, charging for time makes sense.
Instead of Instance-hours, it could be time. On Mon, May 23, 2011 at 2:09 AM, Anders <[email protected]> wrote: > Oh, you're right! Separating CPU and RAM usage would be a good idea (if it > can be done in practice). The price model already contains a large number of > different quotas for all kinds of APIs and stuff. Separating CPU and RAM > usage would not add much complexity. There is still of course the problem > with how to measure CPU time. Is idle CPU time included, or is 100% CPU load > the only measurement or is some other average combination used? > > -- > 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.
