5 ms·
There were a lot of complaints from people that had infrequently used (new) web apps, and so there would be a substantial delay to spin up an instance when the
by fletchowns 15y ago
There were a lot of complaints from people that had infrequently used (new) web apps, and so there would be a substantial delay to spin up an instance when the app did get hit. This makes your site seem "slow" even though it really isn't, which is a big problem if you are trying to build some momentum, or show off your site to potential investors. People were resorting to some less than ideal ways for keeping their instances warm, more information on the app engine for java group: http://code.google.com/p/googleappengine/issues/detail?id=2456 http://code.google.com/p/googleappengine/issues/detail?id=24...
- gte910h 15y agoOh I've used some of the "less than ideal" things during demos before. It truly was an underserved need within the ecosystem.
- uriel 15y agoThat is only a problem for Java apps (and for Python apps using things like Django that were never really suited to AppEngine). None of my AppEngine apps ever had any problem with 'cold' startup speed, and now with Go startup speed will be even less of an issue.
- bemmu 15y agoI believe you can use a feature called "Always On" to avoid the cold start problem. I noticed such an option in my billing settings for $0.30 / day.
- gte910h 15y agoThe always on feature in december fixed half the issue (cold start) This fixed the other half (long running processes).