<small id='REgwF'></small><noframes id='REgwF'>

<tfoot id='REgwF'></tfoot>

<i id='REgwF'><tr id='REgwF'><dt id='REgwF'><q id='REgwF'><span id='REgwF'><b id='REgwF'><form id='REgwF'><ins id='REgwF'></ins><ul id='REgwF'></ul><sub id='REgwF'></sub></form><legend id='REgwF'></legend><bdo id='REgwF'><pre id='REgwF'><center id='REgwF'></center></pre></bdo></b><th id='REgwF'></th></span></q></dt></tr></i><div id='REgwF'><tfoot id='REgwF'></tfoot><dl id='REgwF'><fieldset id='REgwF'></fieldset></dl></div>

      <bdo id='REgwF'></bdo><ul id='REgwF'></ul>
    <legend id='REgwF'><style id='REgwF'><dir id='REgwF'><q id='REgwF'></q></dir></style></legend>
    1. 每 4 分钟发送一次保持活动请求时,Azure Functions 在消费计划中仍然“冷启动"

      时间:2023-10-25
          • <bdo id='RLzhS'></bdo><ul id='RLzhS'></ul>
          • <i id='RLzhS'><tr id='RLzhS'><dt id='RLzhS'><q id='RLzhS'><span id='RLzhS'><b id='RLzhS'><form id='RLzhS'><ins id='RLzhS'></ins><ul id='RLzhS'></ul><sub id='RLzhS'></sub></form><legend id='RLzhS'></legend><bdo id='RLzhS'><pre id='RLzhS'><center id='RLzhS'></center></pre></bdo></b><th id='RLzhS'></th></span></q></dt></tr></i><div id='RLzhS'><tfoot id='RLzhS'></tfoot><dl id='RLzhS'><fieldset id='RLzhS'></fieldset></dl></div>

            <small id='RLzhS'></small><noframes id='RLzhS'>

              <tbody id='RLzhS'></tbody>
          • <legend id='RLzhS'><style id='RLzhS'><dir id='RLzhS'><q id='RLzhS'></q></dir></style></legend>
            <tfoot id='RLzhS'></tfoot>

                本文介绍了每 4 分钟发送一次保持活动请求时,Azure Functions 在消费计划中仍然“冷启动"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                问题描述

                我已经阅读 了解无服务器冷启动|Azure 应用服务团队博客 文章.评论之一说您也可以通过每隔 4 分钟从 Azure Logic 应用调用函数来避免消费计划中的冷启动.

                I already read Understanding Serverless Cold Start | Azure App Service Team Blog article. One the the comments said You can avoid cold start in consumption plan also by calling function from Azure Logic app in every 4 mins interval.

                我试图每 4 分钟向我的应用程序的一项功能发出 1 个请求,但这并不总是有效.它有时仍然是冷启动.我知道这是一个黑客.有没有更好的方法来保证App在使用Consumption plan时始终运行?

                I was trying to make 1 request per 4 minutes to one function of my app but this doesn’t always works. It sometimes still cold start. I know it's a hack. Is there any better way to ensure App always running when using Consumption plan?

                推荐答案

                我试图在我的文章中回答这个问题 Azure Functions 中的首次请求之外的冷启动.

                I tried to answer this question in my article Cold Starts Beyond First Request in Azure Functions.

                简而言之,似乎没有办法完全避免冷启动.保持活动调用将延长给定实例的生命周期,但不会无限期延长.

                In short, there doesn't seem to be a way to avoid cold starts completely. Keep alive calls will make the life span of a given instance longer, but it won't make it indefinitely long.

                目前,冷启动似乎是 FaaS 实施的真正问题,它们会随着时间的推移得到优化,但您可能无法将它们减少到 0.

                For now, Cold Starts seem to be a genuine issues of FaaS implementations, they get optimized over time, but probably you won't be able to reduce them to 0.

                这篇关于每 4 分钟发送一次保持活动请求时,Azure Functions 在消费计划中仍然“冷启动"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                上一篇:Azure Functions 中的 HttpClient 最佳实践 下一篇:部署的 Azure Function (v2) 未运行

                相关文章

                  <legend id='Dr6Ue'><style id='Dr6Ue'><dir id='Dr6Ue'><q id='Dr6Ue'></q></dir></style></legend>

                  <small id='Dr6Ue'></small><noframes id='Dr6Ue'>

                  <tfoot id='Dr6Ue'></tfoot>
                    <i id='Dr6Ue'><tr id='Dr6Ue'><dt id='Dr6Ue'><q id='Dr6Ue'><span id='Dr6Ue'><b id='Dr6Ue'><form id='Dr6Ue'><ins id='Dr6Ue'></ins><ul id='Dr6Ue'></ul><sub id='Dr6Ue'></sub></form><legend id='Dr6Ue'></legend><bdo id='Dr6Ue'><pre id='Dr6Ue'><center id='Dr6Ue'></center></pre></bdo></b><th id='Dr6Ue'></th></span></q></dt></tr></i><div id='Dr6Ue'><tfoot id='Dr6Ue'></tfoot><dl id='Dr6Ue'><fieldset id='Dr6Ue'></fieldset></dl></div>

                    • <bdo id='Dr6Ue'></bdo><ul id='Dr6Ue'></ul>