Hi Depending on the type of application (read or write oriented) and how aggressive you can cache stuff then I would say it is fine for small businesses and/or low volume sites just starting out. However I would look carefully at what you are trying to do and see if it in fact matches app engines architecture, and how you can address your startup times).
I have a small business (in addition to developing full time on app- engine) and its website would be classed as a very low volume site. Typically we between 30 - 50 unique visitors per day, 100-200 page views per day. Our business (bricks and mortar) is heavily dependent on our web traffic. A cold start with content in memcache takes about 300ms (I can serve content from memcache without starting the full app framework). Serving content from memcache on a warm instance is typically less than 20ms. A cold start with a full app framework startup plus doing some real work typically takes no more than 12000 ms (though often a lot less, about 4000ms is more typical). I do not run anything to keep instances warm (like cron). I might actually experience a deadline exceeded about once a week (which I put down to data-store latencies which I am sure will improve). I am using python, so have no experience with java startup times. On the whole we are very happy with app engine, and its performance for a low volume site Regards Tim Hoffman On Jun 11, 1:09 am, ADRA <dche...@gmail.com> wrote: > Hello all, I'd like your opinions on the reality of App Engine > scalability. I'm not so concerned about the the high end, since I'm > nowhere near creating a substantial amount of traffic. In fact, I'm > just starting out at the bottom, and that seems to be a problem with > the system. Today I looked at my logs and found that 90/200 > transactions resulted in cold starts... Mind you, this is from a > service that's basically running a cron job once a minute (site isn't > launched yet, so all its doing are some very light cleanup jobs) > > Is app engine capable of accommodating the business of small guys who > are looking to start out at low volumes, or is the service only really > conducive to high volumes? > > I looked at the status page, and it said that datastore is still in > the suck, but nothing relating to any other server issues. If 45% of > my traffic is going to result in cold starts, then I might as well > give up with app engine now. If a transaction is 4/5's startup and 1/5 > doing work, I can't justify the service's initially appealing > affordability. I might as well just rent out my own fully fledged JVM > that I at least have some measure of control over for LESS money. > > In general I've been very fond of the idea that App Engine would suit > my business needs, but the more I use it in development, the more and > more I find that it'll either cost much more (not related to anything > my code), or it'll have a high time penalty for users. > > (Note: Xposted from AppEngineJava. Sorry for the dupe, but this I > should have posted it here anyways) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
