Brandon, you talk a lot of shit for a guy who only discovered the task queue 6 months ago.
Everyone who thinks they have the secret to starting up a Java app in <5s, answer these questions and prove that you're running more than a toy: * How do you persist data? (low-level, jdo, objectify, etc) * How many entity kinds/classes do you have? * How do you manage URL routing? (ie, jsp files? web.xml? JAX-RS) * How many URL endpoints do you have? * How many total java classes in your application? What is total size? * How many jars in your WEB-INF/lib? What is total size? Having done a fair bit of experimentation around this issue, I know that you're talking out of your asses. Clever suggestions like "rewrite app in Python" aren't nearly as clever as you think they are. Suggestions that you can optimize startup time by some combination of caching, task queues, or threading merely indicate total lack of understanding of the problem in the first place. To the people paying attention to this thread who are actually trying to build real world apps on Appengine: Brandon does not speak for the GAE team. Neither do I, but I occasionally talk to people that do. I know that Google really does want Java apps to run well on GAE. They know about this issue and care about it - maybe even enough to do something about it. It *is* constructive to "whine" politely about startup time because there are many issues competing for the team's time, and our feedback helps them prioritize their efforts. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
