On Thu, Aug 8, 2013 at 1:25 PM, aloo <[email protected]> wrote: > > I haven an appengine app and we currently do about 5-10 deploys per day. > These deploys all have a NEW app version and are then set to default. > > We notice that while switching over the default version, we get about a > minute or 2 of instability while instances are switching over. >
Use traffic splitting ( https://developers.google.com/appengine/docs/adminconsole/trafficsplitting ) to incrementally move more and more users to the new version of an application. That buys time for instances to spool up for the new version and spool down for the previous version. On Thu, Aug 8, 2013 at 1:25 PM, aloo <[email protected]> wrote: > > We plan on increasing the number of deploys to 30/day. Does it make sense > to still deploy to a new version everytime? > > What are the best practices here? How do you handle a lot of deploys? > Is there a particular reason that you need to deploy new versions so rapidly? 30 deploys a day is fine for a test/low-production application, but if you're a high-traffic app it's a good idea to deploy on a much less frequent basis. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
