i think there are other threads on this (or at least similar) topics. i have multiple live apps on GAE:
www.starmakerstudios.com (plus iOS backend services) www.diginn.com www.elizabethscanvas.org they all have *very* different usage profiles and costs. given that i have spend 0 hours doing sysadmin on production GAE servers in years it has been worth it to me. my largest app probably would need at least a half time sysadmin to keep running smoothly. though i did get bit by google's pricing model change last year and it took lots of developer hours to adjust to the new pricing....but we have cleaner much more efficient code as a result. instances run from 1 to as much as 40 depending on which app/traffic. my highest usage app gets 30-50 requests per second on average. i use datastore cause cloud SQL didn't exist when i started. i suspect datastore is cheaper, though i don't know. it depends on your app type for hosting on GAE. don't do stats processing on GAE - the request limitations are horrible to deal with. if you serve lots of short requests that display small/medium amounts of data, or update individual bits of data at a time it seems to be pretty good. think through the types of request you want to do, and the costs of sysadmin vs working in the GAE way. that should give your a way to frame your debate. feel free to ask more questions.... cfh On Thursday, August 9, 2012 2:16:56 AM UTC-7, Alexei Vinidiktov wrote: > > Hi, > > If you run a web2py powered app on GAE in production, could you share your > experiences? > > Is it very expensive for your needs? Are you OK with the pricing? > > How many instances do you run simultaneously on average? > > What kind of traffic do you get? > > How many requests per second do your apps serve? > > Do you use Datastore or Cloud SQL? Why? > > Would you recommend hosting web2py apps on GAE? > > Thanks! > > -- > Alexei Vinidiktov > --
