![]() ![]() Scale VM and disk sizes up and downĬonsider the time a VM is actually running versus when it is stopped (when you do not need it). In my case, the running time is a small percentage. Because of that, I can justify to scale up the sizing so the machine is a lot faster when I use it. There is a lot of public documentation about VM sizes and disk sizes and what workloads are better for some than others. ![]() I am not repeating this here, but just want to share my approach. I encourage you to experiment and share your comments. Important note: The disk sizes incur cost even when the VM is stopped. VM size (VM/Settings/Size): Standard DS13-4_v2 (4 vcpus, 56 GiB memory)ĭisk size for all disks (each disk/Settings/Size + performance): Premium SSD LRS Powershell scripts to scale up and down VM size (VM/Settings/Size): Standard B8ms (8 vcpus, 32 GiB memory)ĭisk size for all disks (each disk/Settings/Size + performance): Standard HDD LRS My High-performance config for a started vm (very fast) Make sure to understand this! My Low-cost config for a stopped VM (cheap) It is not enough to stop a VM, it must be also scaled down. I am sharing 2 scripts that take care of the scaling. You can run them right in the Azure portal’s Cloud Shell. Configure your resource group name and VM name and past them into it. When I want to use the VM, I run the scale up script and start the VM. When I am done using the VM, I run the scale down script (which also stops the VM). Note: This is now also part of the official documentation on : Use Azure Data Explorer to query raw information logs – Finance & Operations | Dynamics 365 | Microsoft Docs. MICROSOFT DYNAMICS POS PADSS SERIAL NUMBER. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |