I was just thinking about this, great idea! 0.1$'s for 1 hours is already A LOT
since it's 35mb/hour for python apps ( assuming a request consumes 35mb's of memory), Let's compare it to a dedicated server with 12gb's ram and 200$ monthly fee: That would make 342 instances, 0.58$ monthly for every instance, 0,020$'s daily, <0.001$ hourly So compared to a dedicated server we currently pay x100, which is acceptable-ish, but x200, x300 would be too high Memory was always a bottleneck for me while managing LAMP, basically a server's capacity is Ram/Request_Consumed_Ram requests every moment And since Web is shaped around API's that consume a lot of time while data is being transferred, memory being the bottleneck should be valid for nearly everyone Megabyte hours would be a great solution On May 15, 4:51 pm, Dale <[email protected]> wrote: > According to Ikai and other Googlers a very real cost to GAE is the > memory consumption of apps that don't use a lot of CPU but still have > active instances. > > So why not add a charge for memory usage x time? If one instance used > 20 MB for 24 hours it would consume 480 MB.hours. > > Instance.hours hides behind an opaque scheduler. I prefer the > granularity of the existing billing system: It's easier to know where > to spend development time optimising code, and what the payoff is > likely to be. -- 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.
