Well, both Baz and Shawn are correct. Shawn is correct from the economical point of view. Baz is correct from the techinical point of view (no sane user would wait 15 seconds for a page to appear, right?).
The great thing is that both can be done at the same time. Warmed instances can be brought up in the background without the user knowing about it. Cheers, Guillermo. On Mon, Mar 29, 2010 at 9:01 PM, Shawn Brown <[email protected]>wrote: > > It's boggled my mind from day 1 why instances > > aren't loaded in the background. I always assumed it would be addressed > > What is difficult to understand? > > 1 server has X resources > warmed instanced require Y resources > > X - YN = resources left over for the server to fulfill requests. > > By reducing N (the number of warmed instances), you can increase the > capacity to fulfill actual requests. > > By allowing us to pay for our own N, Google can presumably increase > the capacity of each server or can increase the number of servers. > > I can see how it can cost Google to have unused apps loaded and ready > to immediately serve. Can't you. > > I don't see what the difficulty understanding is. > > Shawn > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Saludos cordiales, Guillermo Schwarz Sun Certified Enterprise Architect -- 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.
