As a starting point, it is reasonable to plan 12 virtual machines per physical core, and then run the appropriate scenarios to validate performance and density. Higher density may be achievable depending on the specifics of the workload. We recommend enabling hyperthreading, but be sure to calculate the oversubscription ratio based on the number of physical cores and not the number of logical processors. This ensures the expected level of performance on a per CPU basis. Server virtualization, as far as I have seen, is still 8 vCPU's per logical processor or threads.
Soooo, it looks like in VDI they like to go by physical core, and in general server virtualization, they like to go by logical processors or threads.
So "technically", you don't go by hyperthreading, but realistically, hyperthreading will give you more physical logical processors. Not that you'd actually be able to use all of those without any performance issues, but technically speaking Planning a new environment, I wouldn't count the logical processors that are the result of hyperthreading.
I would just add a fudge factor to any calculation based on the actual core count. In an existing environment, we have various tools, as well as user feedback, to gauge whether we've gone too far in overallocating vCPUs.
Interesting article, Tim. Seems to come down to workload and circumstance. And yes, virtual desktop workloads are different from server workloads. That affects RAM, and nowadays disk, usage as well. When you have a hundred almost identical VMs running on a host or storage array , there are opportunities for additional optimizations. If you are using dynamic memory or -pre-allocated memory, if you are using vcentre how you have configured it to handle ram usage - you can choose to continue anyway or abort, if you have GB of physical ram and 1TB allocated, I would expect issues, however if you have GB of ram and want to allocate gb I can't see this being an issue, unless your settings prevent more being powered on.
Ah, didn't think about dynamic memory. I don't use dynamic memory. The few times when I've implemented it I immediately received calls from users complaining about poor performance. This has been the case with multiple physical hosts in different environments. It's always felt like it did back in the day when using a Celeron vs. To continue this discussion, please ask a new question. Anunta Followers - Follow. Kelly for Anunta. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Best Answer. Thai Pepper. The domain contains a member server named Server1. Server1 hosts 10 virtual machines. Users report that App1 responds more slowly than expected.
You need to monitor the processor usage on VM1 to identify whether changes must be made to the hardware settings of VM1. Processor B. Maybe i am missing something. I come from a VMWare environment. So is hyver processors equal to Vmware cores? Just trying to transition between the two. Maybe you can help me with a issue, Is it anyway to assign a physical processor to a virtual machine?
I think this is an option in VMWare. There is no way to physically peg a virtual processor to particular CPU or core. There is a direct one to one relationship, but this is a dynamic allocation. Even if there was away of doing this I would not recommend it. One of the main advantage of using type 2 hyper visors like ESX and Hyper-V is that they can dynamically optimise the virtual machines based on the on the cumulative virtual machine load and the net hardware availability.
A stupid question probably. I have a virtual terminal server running. Users are having issues with delayed typing. Is that systems cpu is fully loaded or what to do so the virtual machine uses full capacity. Relative weight There are a number of terminal server specific configuration options you could look into to try help things along.
A similar issue is found on this section:. Or am I missing something? Since this setup evrything has terribly slowed down. I have one Virtual processor. Currently virtual machine reserve is at 0,virtual macjine limit is at , relative weight at as well. Save my name, email, and website in this browser for the next time I comment. What is Fastvue Reporter? Previous Next. About the Author: Etienne Liebetrau. Based in Dublin, Ireland Etienne is an IT Professional working in various environments building, testing, and maintaining systems for a diverse customer base from various business verticals.
Etienne is a technical trainer, writer, and blogger. Related Posts. Steven Kornegay December 12, at pm - Reply. Dual UPI up to A physical to vCPU correlation of 1-to for non-intensive workloads can further increase these numbers.
These server families can support upto 6TB of physical memory providing enough memory to be allocated to the VMs without hitting performance bottlenecks. This amounts to TB of total storage space. This provides adequate storage distribution options for the guest VMs. Both server families come with a standard three year warranty which can be further enhanced to extended or on-site support.
Conclusion and server families score well among all the hardware considerations mentioned earlier in the article and the available configuration options cater to a very wide range of possible requirements. From hosting a few VMs to plus VMs, these server families can scale well to serve a diverse set of workloads. Considering the configuration options, extensibility and scalability, and value for money and support, and Ultra Server series are among the best server hardware to run a virtualized environment.
You can read more about these server families here. Learn more about Hyper-V in our post, These are the […]. More memory is better. You'll need enough memory for the host and all virtual machines that you want to run at the same time. Hardware-assisted virtualization. For Intel systems, this is the XD bit execute disable bit. Here are the requirements for discrete device assignment and shielded virtual machines.
For instructions, see the hardware documentation or contact your hardware manufacturer. For GPU, only certain devices support discrete device assignment. To verify, see the hardware documentation or contact your hardware manufacturer. For details about this feature, including how to use it and considerations, see the post " Discrete Device Assignment -- Description and background " in the Virtualization blog.
0コメント