Getting more storage capacity for data or applications is not a problem. The question is: how fast your apps can run? That’s why performance becomes a number 1 demand for the majority of system administrators. So it’s not a big deal finding an article on improving Hyper-V and VMs performance, the challenge is to get an up-to-date info and modern insights. That’s why in this post, I’m gonna give some advice on boosting your Hyper-V infrastructure performance – from host to virtual machine and the overall cluster optimization. This might come in handy when building a new Hyper-V based environment or even improving the existing one. Let’s put the pedal to the metal!
Today, I’ll talk about a thing that any sysadmin running Hyper-V VMs does (or still dreams about) while managing infrastructure resources: hot modifying assigned to VM memory amount. I’ll discuss not only the feature itself but also how it works on different OS and its impact on the environment stability.
All of us keep an eye on resource consumption within our environments. If a VM needs extra RAM to have the job done, we provide it with some, right? And, we usually run many VMs on our servers each with own purpose and configuration. That’s, actually, why changing the amount of assigned to a VM memory without rebooting it may come in handy. Also, many guys run some parts of their environments on Windows while having other parts run on something from Linux family. Looks pretty hectic in terms of management, doesn’t it?
What’s new in Windows Server 2016
Windows Server 2016 differentiated Standard and Datacenter licenses. The functions available to Datacenter users are mentioned below:
- New storage functions (including Storage Spaces Direct and Storage Replica)
- New shielded Virtual Machines
- The new network stack
The features enabled in new editions are designed for virtual environments. It should also be noted that Windows Server 2016 supports Docker-powered Windows Server containers
Fortunately, Windows containers are available without any additional licensing and do not have any restrictions regarding the number of running instances. The storages are expected to be available on Pro and Enterprise Windows 10 version, starting from the 1607 (Anniversary Update) one.
Subscribe to our posts
- How is NVMe-oF doing? Part 1: Linux NVMe-oF Initiator + Linux SPDK NVMe-oF Target
- Setting up a Windows Failover Cluster for a home lab
- Performance comparison: SQL Server Failover Cluster Instance on S2D vs. SQL Server Basic Availability Groups on Storage Spaces. The battle starts
- Can SQL Server Failover Cluster Instances run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 2: Studying FCI performance
- Can SQL Server Failover Cluster Instance run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 1: Studying BAG performance