6 Best Practices for Physical Servers Hosting Hyper-V Roles

From the Microsoft Press ebook Understanding Microsoft Virtualization Solutions: From the Desktop to the Datacenter by Mitch Tulloch.

  • Avoid Overloading the Server
  • Ensure High-Speed Access to Storage
  • Install Multiple Network Interface Cards
  • Configure Antivirus Software to Bypass Hyper-V Processes and Directories
  • Avoid Storing System Files on Drives Used for Hyper-V Storage
  • Monitor Performance to Optimize and Manage Server Loading

Here are 23 Best Practices to improve Hyper-V and VM Performance

by Nirmal Sharma

  1. Avoid overloading Hyper-V Server
  2. Avoid creation of multiple Virtual Network Switches
  3. Configure antivirus software to bypass Hyper-V processes and directories
  4. Avoid Mixing Virtual Machines that can or cannot use Integration Service components
  5. Avoid storing system files on drives used for Hyper-V storage
  6. Use separate volumes for each VM
  7. Avoid single point of failure for network adapters using NIC Teaming
  8. Always use Network Isolation Mechanism rather than creating a separate virtual switch
  9. Install Multiple Network Interface cards on Hyper-V Server
  10. Always use supported guest Operating Systems
  11. Always use Generation Type 2 Virtual Machines
  12. Always change the default location for storing virtual machine configuration and VHD files
  13. Monitor performance of Hyper-V Server for optimization
  14. De-fragment Hyper-V Server regularly or before creating a virtual hard disk
  15. Always install the Integration Components on the supported virtual machines
  16. Always use Fixed VHD files
  17. Use Dynamic Memory Feature
  18. Configure SCSI disks for Data volumes
  19. Relocate paging file to a SCSI Disk Controller
  20. Always exclude Paging file for virtual machines participating in Hyper-V Replication
  21. Implement Hyper-V in Server Core in Production environment
  22. Close unnecessary Windows
  23. Use Certified Hardware

Maximizing Hyper-V Performance

Learn the best practises to optimize Hyper-V by Michael Otey

Hyper-V Host Performance Tips

Hyper-V offers extreme scalability with VM’s of up to 64 vCPUs and 1 TB of RAM. However, in order to maximize the performance of your Hyper-V platform there are several best practices that you should follow for the both the Hyper-V host and VM guests. For the host:

  • Reserve the parent partition for Hyper-V — Do not run other roles or applications in the parent partition. The parent platform should be reserved for managing Hyper-V. Running other applications in it will degrade of the performance of all your VMs
  • Reserve 1GB for Hyper-V partition – The parent partition needs RAM to manage the various VMs and worker threads. Don’t allocate all of the available RAM to the VMs.
  • Don’t over allocate your cores – For maximum performance ensure the each VM has a physical core to handle its workload. A rule of thumb for the best VM performance is 1 CPU core per vCPU.
  • Don’t run Hyper-V Manager all the time – Hyper-V Manager is an application and will take resources form your VMs. Don’t leave it up all the time. It’s better to manage Hyper-V from a networked system.

Hyper-V Guest VM Performance Tips

For the guest Hyper-V VMs you should:

  • Use enlighten guest OSes – Enlightened OS can take advantage of higher performance synthetic drivers that use fewer host CPU cycles.
  • Consider separating the paging file from the boot drive – Separating the I/O of the paging file can help improve VM performance. Use a VHD or VHDX that is sized at 1.5x the VM RAM.
  • Don’t use checkpoints on production servers – Checkpoints are great for test, lab and help desk systems but they increase I/O requirements which will degrade the performance of production servers.

The New Way

If you’re looking for a very modern way to check and monitor performance, you should give Performance Analyzer a try.

Monitor and Analyze Microsoft Hyper-V configuration and performance metrics. Correlate events and metrics in guest applications and infrastructure with Hyper-V metrics. Troubleshoot issues using our efficient data crawler and preconfigured dashboards.

Microsoft Hyper-V

Some of our VMware vSphere integration features are:

  • Find Disk I/O bottlenecks
  • Full insights into Disk Latency and VM Disk IOps
  • See Memory Issues (Swapping) and Network Issues (Packet Loss) instantly
  • See Host OS (MS Windows) bottlenecks and most important performance metrics

Microsoft Hyper-V

Sign up for Performance Analyzer today and start 30 days for free.

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.