On Mar 4, 6:51 pm, Jeff Schnitzer <[email protected]> wrote: > THE COLD START PROBLEM WILL NEVER BE SOLVED. ... > Yes, Google could give you the option to pay for a "warm" instance, > but it will only reduce - not eliminate - cold start times. Users > will still see them when you redeploy your app, when a new instance > spins up to handle load, or when your instance migrates off of a hot > server.
Really? Are you absolutely certain that it is technically impossible to spin up an app *before* handing it over to users? Are you confident that the laws of physics prohibit spinning up new instance of apps in the background after deployment? Though I've never developed an appserver myself, I suspect your assertion about the infeasibility of this particular problem is incorrect. I don't know how big the appengine team is, but it certainly would be reasonable for Google to devote a few more resources to the project, considering its popularity and the constant stream of users asking for a specific feature. I'm not sure if Robert's method of complaining loudly all over the internet would cause Google management to react or not, though. I just reworked my apps so that they run on multiple different platforms, and I'm watching appengine closely in hopes that I can move back to it once the bugs are worked out. You can get a VPS from the likes of RackSpace for $11/month. Such a solution requires a little more sysadmin work, but that's preferable to giving users random 500s due to "excessive latency" and whatnot. -- 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.
