不使用已弃用的 vm_settings - > machine_type 设置，我的Google托管虚拟机部署为 g1-small 。使用作为一个模板，除了 memory_gb 之外，还需要做些什么来部署为 f1-micro 机器类型？目前，我有
资源：
cpu：.5
memory_gb：.6
disk_size_gb：10
并使用
部署 gcloud预览应用程序部署app.yaml --set-default
vm_settings：
machine_type：f1-micro
...的作品，但我被警告说这个设定很快就会消失。
我不得不下降到.18才能将其部署为f1-micro，但总体思路是谷歌正在增加开销是坚实的。
Without utilizing the deprecated vm_settings -> machine_type setting, my Google Managed VM deploys as g1-small. Using Node.js app.yaml as a template, what do I need to change besides memory_gb to deploy as an f1-micro machine type? Presently, I have
resources:
cpu: .5
memory_gb: .6
disk_size_gb: 10
and deploy using
gcloud preview app deploy app.yaml --set-default
doing
vm_settings:
machine_type: f1-micro
...works, but I'm warned that this setting will soon disappear.
As Jeff and Greg both replied, "Google adds a little overhead on the VM before picking a machine type. This is around 400mb of ram. So they told me if you want an f1-micro try requesting .2 or lower memory as Greg mentioned."
I had to drop to .18 to get it to deploy as f1-micro, but the general idea that google is adding overhead is solid.
这篇关于在app.yaml中为Google云计算node.js应用设置无vm_settings的f1-micro资源限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！