Appengine has got two modes of operation.
High traffic applications are served directly out of the cache within a second for example. For low traffic applications first the uploded code has to be prepared (unzipped for example) and put into the cache before it can be served. Thus low traffic applications necessarly need a longer request time - three seconds for example. To my experience low traffic is everything below about 500 requests per hour. > New machine instantiations, which we all know happens quite frequently New pages usually haven't a lot of visitors yet and thus are low traffic apps. But a lot of longer existing pages have got low traffic too. Low traffic means additionally that each request consumes more resources. Usually that doesn't matter as for almost all low traffic pages these additional resources stay within the free quota. -------------------- When comparing perfomance of different solutions it's important that the solutions themselves are comparable. If you don't need session management, user name, user account and administration you probably don't need Django and should use a simple and faster solution. What concerns the performance of a Django solution my tests with the aep-sample copied to my own appID three month ago varied for high traffic between 0.5 - 1.0 seconds request time for low traffic between 2.5 - 4.5 seconds request time I would be very interested to hear of current test results. --~--~---------~--~----~------------~-------~--~----~ 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-appengine@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 -~----------~----~----~----~------~----~------~--~---
