本文介绍了自定义Azure Batch VM启动缓慢的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用自定义Windows Server 2016映像(带有VS Community),分配后,vm花费了10分钟以上的时间来准备执行批处理任务.通用Windows Server 2016花费不到3分钟,几个月前,自定义数据科学窗口 2016花了我5分钟才能开始.

I am using a custom Windows Server 2016 image (with VS Community) and after allocation the vm takes more than 10min to be ready to execute batch tasks. A generic Windows Server 2016 takes less than 3min and a a few months ago a custom datascience windows 2016 was taking me 5min to start.

是否有办法了解问题是否来自图像的泛化?

Is there a way to understand if the problem comes from the process of generalizing the image?

推荐答案

我建议调查的一件事是节点之一的系统日志.

One thing I would suggest looking into is the system logs of one of the nodes. 

如果您转到批次帐户->泳池->节点->选择一个节点

If you go to your batch account -> Pools -> Nodes -> Select a node

您可以RDP到物理节点.您可以从那里查看系统和应用程序日志,以查看初始化VM时正在启动的内容.这可以使您了解为什么要花时间.

you can RDP to the physical node. From there you could look into the system and the application logs to see what is starting up when the VM is being initialized. This might give you some insight into why it is taking the time it is. 

我建议您从启动时间开始,直到发现执行任务的时间为止.这样,您就可以汇总所有服务的列表.从那里,您可以尝试创建第二个映像,并限制所有不需要的启动服务.

I suggest looking from startup time to the time you find the task is being executed. That way you can piece together a list of all the services. From there, you could try creating a second image and limit any startup services that are not required. 


这篇关于自定义Azure Batch VM启动缓慢的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-06 00:07