I'm using a combination of Spring, Objectify and Spring Security. App spins up in 20 secs. Could be a lot faster if I was not using classpath scanning. But with always up and correct warmup request config, anything under 30 secs will do just fine.
What you want is to get sub 10 secs startup in dev mode so that your unit tests start up fast. On Apr 19, 4:24 pm, "[email protected]" <[email protected]> wrote: > What is a good/acceptable application load time? The load time of my > application in "run" mode in the development environment gives me a good > confidence of the real application load time on production environment? > > Loreno > > On Tue, Apr 19, 2011 at 5:18 PM, Marcel Overdijk > <[email protected]>wrote: > > > > > No check out docs about Warmup requests: > > >http://code.google.com/appengine/docs/java/config/appconfig.html#Warm... > > > On Apr 19, 1:18 pm, Nischal <[email protected]> wrote: > > > You mean you have reserved instances? IMO you would still need to take > > care > > > of your load time as new instances are spun off when your traffic > > increases > > > and if your load time is too much then it would lead to errors while > > > spinning up new instances. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" 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-java?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
