I don't buy the $30 - $40 / month figure for GAE. With just a tiny bit of tuning, my single-threaded M/S app is now running on just one instance, handling both periodic robots (that keep the instance from dying; this is unavoidable in my application), and a regular user workload:
You can clearly see the point at which I deployed my tuning. :) I'd want to have the capacity for the occasional (rare) spin-up from concurrent user access, so I'd go for the $9/month plan. Let's assume, for the sake of argument, that people take the time to optimize like I did, and also that they take advantage of edge caching. And also, the site is small, so GoogleBot isn't going to go for the periodic kill (I've never seen GoogleBot assault my site). So I think the right number for GAE for the scenario you laid out is $9. Not $30-$40. On Sep 4, 2011, at 9:26 AM, Tim Hoffman wrote: > Hi > > More than a few people have said in the groups lately that appengine is > unsuitable for entry level apps due to the new pricing schedule. > I am not so sure, but there hasn't been any real information about the > alternatives, so I thought I would start to collate some numbers > > So to that end I have included a spreadsheet here with a summary of a number > of VPS or cloud providers solutions that I would consider > might be suitable to run a small entry level appengine app. > > For the sake of the discussion you would want to run a stack that looks like > the following > > linux > nginx/apache > a light weight stack say webapp2, pyramid, tipfy (a lightweight framework) > an ORM (sqlobject/Storm) > and mysql > > This doesn't really equate to a heroku offering, but lets say in each case > we need a single instance of something running, 512MB at a minimum to run the > small stack and an RDBMS , with at least 1GB of > storage available if no OS is factored in and 5GB if the OS counts in the > storage allocation. > > So here is a spreadsheet. > https://docs.google.com/spreadsheet/ccc?key=0At1LTa6ONStgdExuRUl2QUdOVE0yWDFDbUJyX09QNlE&hl=en_US > > I know none of these compare service wise directly with appengine. But these > are the sort of services people name > frequently as viable alternatives that are cheaper than appengine. So lets > look at the reallity > > The equivalent appengine basic service would be a single permanently idle > instance running 24 hours a day, plus low volume of traffic and < 1GB of data > in the datastore. So more instances might spin up. Under 2.7 with threading > requests we might not see more instance start. A $ figure to apply to such > an appengine app > would probably be between $30 and $40 per month. > > Please suggest refinements to these models, and additonal detail to go into > the spread sheet. > > On the face of it I am not convinced many of these services are significantly > cheaper than appengine especially when you take into account most of them > require you to manage the complete stack. > > Hope this helps focus the discussion and provide some reality checks. > > I personally have no plans to move off appengine. But due plan to do some > tuning. > > Regards > > Tim > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/khEdCXoWqpsJ. > 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.
<<inline: PastedGraphic-3.png>>
