when we really carefully using python (like lazy loading almost every single thing ) -- the cold start is not an issue......the problem with app engine is the lack of de-facto standard on what gives best performance and solutions to many small problems -- like how to design an app heavily lazy loaded , what is the best way to partition data, unique property , timeouts retry , cpickle marshal or protobuf -- give something fast enough please..., subdomains , full text search , mapreduce and cursor , how to create better counters -- this should be built in -- a counter library ( start this issue: http://code.google.com/p/googleappengine/issues/detail?id=2491) -- most of this things we can do it on our own -- and it is reliable -- and we can even defer it -- but i still like google providing solutions to such a common problem then having to rely on some third party library or coding our own workarounds....
-- 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.
