Hi Paul, Thanks for the post! Since the launch of "Always On", though, the cold start issue impacts developers far less than before. Everyone we've spoken to will gladly enable billing for the feature if it frees them to use the framework of their choice. One suggestion: break the post into 2 portions, one about startup time, and one about general Memcache/Datastore strategies. This'll allow folks to bypass the tips for startup time if they are simply going for "Always On" and are already set on using a framework with a higher load time.
-- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Mon, Dec 6, 2010 at 4:56 AM, Paul Bakker <paul.bakker...@gmail.com> wrote: > Since I've seen a lot of people with performance problems in their > Java applications on GAE I decided to write an article with some > advices on how to design applications that deal with the differences > of the GAE architecture compared to a normal dedicated server > environment. I hope it's useful and takes away some of the negative > feedback. > http://paulonjava.blogspot.com/2010/12/tuning-google-appengine.html > > -- > 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. > > -- 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.
