Answers: <p>My general experience of Serverless across the three major clouds is that:</p>
  
  <ul>
  <li>GCP takes up to two minutes.</li>
  <li>AWS takes about a minute.</li>
  <li>Azure is a bit random and has bad days when it can take five minutes, but mostly around two minutes.</li>
  </ul>
  
  <p>Some of it rather depends on how you measure it, and what you use to deploy it.  Something like Serverless Framework will do some additional work to creating a CloudFormation template which adds to the overall time. </p>
  
  <p>A former colleague of mine, <a href="https://www.azurefromthetrenches.com/page/2/?s=Azure%20Functions" rel="nofollow noreferrer">James Randall</a>, has published quite a few articles on various aspects of Serverless performance - I haven't seen anything specific around how long it takes for a cloud provider to distribute code to the point of execution, but you may be able to glean some additional answers from his work.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-11-13T10:23:59.340Z
Answers: 2019-11-13T10:23:59.340Z
Answers: Richard Slater
Answers: <p>This will vary based on your cloud provider and what services you are using.  AWS Lambda functions are designed to be highly available for the region.  <a href="https://aws.amazon.com/lambda/faqs/" rel="nofollow noreferrer">Per the AWS Lambda FAQ</a>: </p>
  
  <blockquote>
    <p>When you update a Lambda function, there will be a brief window of time, typically less than a minute, when requests could be served by either the old or the new version of your function.</p>
  </blockquote>
  
  <p>So the new function will not be instantaneously available, and there is a possibility that the old function may be called.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-11-13T03:51:17.607Z
Answers: 2019-11-13T03:51:17.607Z
Answers: Wesley Rolnick
Body: <p>using any method - cli, serverless.com, terraform, roughly:</p>
  
  <p><strong>how much time can i expect to pass between these two steps:</strong></p>
  
  <ol>
  <li>submitting a new function to AWS (or azure or GCF), and </li>
  <li>having that function hosted live in the cloud?</li>
  </ol>
  
  <p>note that i'm <strong><em>not</em></strong> asking about cold start times.  </p>
  
  <p>i'm wondering how long it takes new function code to be entered into and hosted in the AWS lambda system (or azure, ibm, google etc) for a given region.  that is, after taking steps to deploy some new lambda/serverless function code, approximately how soon will i be able to use it?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-11-17T05:03:42.447Z
Comments: just found this article where the author said it took about 3 minutes for AWS https://read.acloud.guru/does-coding-language-memory-or-package-size-affect-cold-starts-of-aws-lambda-a15e26d12c76
Comments: stuart
Tags: <terraform><azure-devops><google-cloud-platform><aws-lambda><openwhisk>
Title: how long does it take to deploy a serverless function?
UserDisplayName: stuart
ThreadText: # how long does it take to deploy a serverless function?
  
  (Asked by: username_0 on 2019-11-12)
  
  using any method - cli, serverless.com, terraform, roughly:
  
  **how much time can i expect to pass between these two steps:**
  
  1. submitting a new function to AWS (or azure or GCF), and
  2. having that function hosted live in the cloud?
  
  note that i'm ***not*** asking about cold start times.
  
  i'm wondering how long it takes new function code to be entered into and hosted in the AWS lambda system (or azure, ibm, google etc) for a given region. that is, after taking steps to deploy some new lambda/serverless function code, approximately how soon will i be able to use it?
  
  **Tags:** terraform, azure-devops, google-cloud-platform, aws-lambda, openwhisk
  
  > **Comments:**
  > **username_0**: just found this article where the author said it took about 3 minutes for AWS https://read.acloud.guru/does-coding-language-memory-or-package-size-affect-cold-starts-of-aws-lambda-a15e26d12c76  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-11-13. Score: 1 | Accepted answer
  
  My general experience of Serverless across the three major clouds is that:
  
  * GCP takes up to two minutes.
  * AWS takes about a minute.
  * Azure is a bit random and has bad days when it can take five minutes, but mostly around two minutes.
  
  Some of it rather depends on how you measure it, and what you use to deploy it. Something like Serverless Framework will do some additional work to creating a CloudFormation template which adds to the overall time.
  
  A former colleague of mine, [James Randall](https://www.azurefromthetrenches.com/page/2/?s=Azure%20Functions), has published quite a few articles on various aspects of Serverless performance - I haven't seen anything specific around how long it takes for a cloud provider to distribute code to the point of execution, but you may be able to glean some additional answers from his work.
  
  
  ---
  
  ### Answer by username_2 on 2019-11-13. Score: 1
  
  This will vary based on your cloud provider and what services you are using. AWS Lambda functions are designed to be highly available for the region. [Per the AWS Lambda FAQ](https://aws.amazon.com/lambda/faqs/):
  
  > When you update a Lambda function, there will be a brief window of time, typically less than a minute, when requests could be served by either the old or the new version of your function.
  
  So the new function will not be instantaneously available, and there is a possibility that the old function may be called.
  
  
  ---
  
  