I am very unclear, even after reading this thread and elsewhere, what impact the scheduler will have on reducing my instances for my python based app.
I don't have a particularly intense app - log some data, analyze some data, push some data into spreadsheets. .62 CPU/hrs/day....6 instances @ 30MB each. I can't imagine what I would code to make them go away. Or do I have to port to Java? I'm paying $50/yr, which is really cheap. However, 5 instances (1 free, right) @ .05/hr = $180/month just for the instances. 6 instances @ 30MB each....$2160/yr... An AWS Micro instance has 613MB of ram and can burst to 2 ECU's and costs $115/yr The $9/mo for single instance looks a lot like AWS pricing (from a $ standpoint) but then you must give us the tools to make things multi- task. I must think that my app uses less resources than something cranking away multi-threaded in a single instance... Looking forward to some docs and maybe some revised pricing.... -Aaron -- 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.
