For the continuous deployment, we use maven EAR to run all together in scripting. We run everything in our local servers, so we don't need to be warming up instances. We had to code our own dispatch.xml handler in order to be able to develop locally in a multi module setup. Since appengine doesn't support that in local.
I have to do the AB trick every single time as well. With the same parameters :) It would be so easy for the appengine team to put a "warmup XX" instances whenever releasing a new version. Although, they're probably busy enabling a new language support rather than making existing customers happy :) thanks rafa On Wed, Sep 25, 2013 at 8:19 AM, Jeff Schnitzer <j...@infohazard.org> wrote: > I don't flood it - I just make one fetch to make sure a single instance is > up. Our app is very busty and usually has low enough traffic that this > prevents any major UX issues. I just wanted to mention it just in case > someone does try this with a high-traffic app. > > Shelling out to 'ab' is pretty simple. This should get a handful of > instances off the ground: > > > ab -n 100 -c 10 http://www.example.com/ > > > See http://en.wikipedia.org/wiki/ApacheBench > > Jeff > > > On Tue, Sep 24, 2013 at 7:14 PM, Aleem Mawani <al...@streak.com> wrote: > >> >> >> On Saturday, August 10, 2013 10:08:01 AM UTC-7, Jeff Schnitzer wrote: >>> >>> We do zero-downtime rolling deployments. Our solution is to deploy to a >>> new version each time (identified by a timestamp), warm up the version, and >>> then switch. If you have a high-traffic app you may need to use something >>> like 'ab' to flood the new version and spin up enough instances. >>> >> Can you describe the proicess you use to "flood" the new version with >> requests? >> >> >> >>> >>> Here's our ant script: >>> https://gist.github.com/**stickfigure/6201192<https://gist.github.com/stickfigure/6201192> >>> >>> Unfortunately there's no API to delete old versions, so every couple >>> deploys we have to go into the GAE admin UI and delete several versions by >>> hand. >>> >>> We're in the process of mavenizing this app so this is all going to >>> change again of course... >>> >>> Jeff >>> >>> >>> On Fri, Aug 9, 2013 at 4:44 PM, Nick <naok...@gmail.com> wrote: >>> >>>> We do continuous deployment as well, although not 30 a day. >>>> I can't quite remember when there started being issues with 500s being >>>> served when deploying an app, but it wasn't always the case. Appengine used >>>> to just handle deploying newer code to the same version and start up new >>>> instances, shutting down old ones naturally. >>>> >>>> We basically have two versions, one set to default, and another used >>>> for smoke test and to host while we're deploying. We upload new code to the >>>> smoke testing environment, smoke test, then switch it to default. Then we >>>> deploy to the other version and flip it back to default. >>>> >>>> Occasionally the behaviour doing this changes (for a while the old >>>> instances on the old version didn't shutdown, and had to be done manually), >>>> but that's the nature of appengine. >>>> >>>> Issue to star if you're interested (this affects everyone, any >>>> deployment will currently cause downtime to consumers for a small window - >>>> 2 seconds to a couple of minutes, there will be no indication of this in >>>> your logs at all): >>>> http://code.google.com/p/**googleappengine/issues/detail?** >>>> id=7874&q=Deploy&colspec=ID%**20Type%20Component%20Status%** >>>> 20Stars%20Summary%20Language%**20Priority%20Owner%20Log<http://code.google.com/p/googleappengine/issues/detail?id=7874&q=Deploy&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to google-appengi...@**googlegroups.com. >>>> To post to this group, send email to google-a...@googlegroups.**com. >>>> >>>> Visit this group at >>>> http://groups.google.com/**group/google-appengine<http://groups.google.com/group/google-appengine> >>>> . >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
