And why so complicated price model? Isn't it possible to normalize difference things like CPU, number of instances, data storage and bandwidth cost etc into a single metric? And then have enough physical servers etc so that too much instance swapping is prevented. With a normalization like that it would be as simple as paying for electricity. The amount of resources an application needs, regardless of whether it's more CPU or data storage or bandwidth or primary memory or whatever, since the resources are normalized they can all be combined into a single parameter, would be like paying for the amount of electricity used.
Too much optimization by having all kinds of parameters for customers to choose between and alter will likely be a suboptimization overall. Some customers may need to fine-tune things on a detailed level, so manual options could be available but also an automatic default price model that would be as simple as paying for electricity. I don't want to regulate the budget manually except for setting a monthly amount. And instead have an algorithm automatically distributing the budget amount for the different kinds of resources. And have statistics presented showing how much the application consumes for each resource type such as CPU, data storage etc, so that I can optimize the application without having to manually adjust the budget distribution. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Sp8E-UQ8QyQJ. 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-java?hl=en.
