Choose 'Chart Options' and under 'CPU', select the metric 'Core Utilization'. 4x physical cores. Each physical processor (CPU) in a server needs to have at least one processor license key assigned to be able to run vSphere. Total RAM per host 6. from another active cluster - 3 hosts 42 virtual machines. With a VM you assign the number of vCPU you want that machine to have, and then pin THOSE CPU to a specific Core on the ESX host. 0 and later versions on first, second-generation Intel Xeon Scalable processors, such as Broadwell, Skylake, Cascade Lake, Cooper Lake and third-generation Intel Xeon. Maximum number of Cost items = 25. 2GB. 3% of the total CPU power of host. This is important when you overcommit vCPU/physical cores. Also, it is important to mention that there is a limitation in the assignation of vCPU which is related to the license of the vSphere you are using. VMware has created a tool to identify the number of per-CPU licenses (supporting up to 32 physical cores per CPU) required for existing. coresPerSocket larger than 64 will result in a. That was accomplished giving half of CPU cycles to each logical CPU. Active CPU is approximately equal to the ratio of the used CPU to the available CPU. 10. Table 2. Considering that 1 vCPU is equal to 1 CPU is an assumption for the sake of simplification, since vCPUs are scheduled on logical CPUs which are hardware execution contexts. Many workstation systems don't have great RAM expansion (many top out at 24GB RAM). 6 Determining Host CPU and Memory Requirements. It is more akin to the share of time that the VM will recive of each clock cycle of the phyical CPU. VMware uses the terms virtual CPU (vCPU) and physical CPU (pCPU) to distinguish between the. vSphere uses dynamic processor load balancing that allows each assigned core in a guest access to all cores on the host. This article provides guidance for reviewing a series of ESX/ESXi host VMkernel and virtual machine failures, and the physical CPUs they are associated with. 11-20-2021 02:00 AM. If you have a physical CPU running at 2. 7. 2) If you have an allocation pool with 12 GHz CPU allocation and a CPU speed of 1 GHz, the customer can use 12 vCPUs (12 * 1 GHz). Cisco design docs say that ESXi reserves approximately 1 core for itself and to take that into account. It is recommendable to leave 10% or more room for CPU bursts. Total number of assigned vCPUs to a VM is calculated as:numa. Only ever use 1 Core per Socket, let vNUMA do it's thing. 0U2 Do the following: 1) Get a reference point from the CPU performance graph. Key stats for the Intel Xeon E-2288G include 8 cores/16 threads with a 3. Guaranteed CPU allocation for this virtual machine. A vCPU is a virtual core that is assigned to a virtual machine or a physical processor core if the server is not partitioned for virtual. An extreme example is that Kinnison's host could quite happily run TWO VMs with 56 vCPUs. I am trying to understand vCPU concept in VMware. and basing it on purely vCPU then 8 would be minimum but would give little room for moving machines around for patching ESXi, covering off high CPU workloads or providing resilience for potential hardware failures, I would recommend a minimum n+1 so 9 hosts. BTW if your search inside the community, you can find many related topics about CPU Sockets and cores relation, like the following links: pCPU vs vCPU - Relation/Ratio. CPU: VMware Horizon DaaS recommends setting a 10x over commit ratio for CPU. pCPU Calculation (# Processor Sockets) X (# Cores/Processor) = # Physical Processors (pCPU) 2 x 20 = 40 pCPU vCPU Calculation (# pCPU) X (2. 0, one CPU license covers one CPU with up to 32 cores. Outputs: Cost items are grouped by type - one-time costs and yearly recurring costs. VMware is one of the top virtualization software that allows you to create virtual machines and make the best use of your resources. coresPerSocket larger than. Without knowing other information like memory network capacity, processor usage etc. Each vSphere license has a certain capacity that you can use to license multiple physical CPUs on ESXi hosts. 4. EG. Select a VM, and go to the performance charts and go to advanced. To the guest OS it looks like a real CPU but on the Hypervisor (ESXi, VMware Workstation,. Here, we select Intel Xeon E-2288G as the underlying CPU. However, there are some machine types that use hyperthreading, which means that a single vCPU can be used to run two. Browse to the virtual machine in the vSphere Client. This should help: (# of Processor Sockets your Server has) * (# of Cores your CPU has) = # of physical Processors (pCPU) now (# of physical processors) * (2 (because hyperthreading)) = # of vCPU'S. If you have an eight-vCPU server, you need two SQL. It is not completely exact and if someone has a better idea, please let me know. Microsoft provides guidelines to calculate the required compute resources for a single instance of Exchange Server (as an application) so that. I am interested in learning more about provisioning. The default parameters used by this tool are for illustration purpose only. It is normal for a VM to average between 0–50 ms of CPU ready time; anything over 1000 ms is considered to lead to VM performance problems. 5 as well. I know that our 2 vCPU TS on vSphere is way faster than 2 vCPU on 3. 1 vCPU, requests are processed quickly. 5. In these cases, keep the CPU overcommitment ratio vCPU-to-pCPU less than or equal to 2:1. a VM with eight CPUs assigned (in any cores per socket configuration) will be referenced as an “eight vCPUs VM”. • 3:1 to 5:1 may begin to cause performance degradation. In general we always start at the lower end of the scale (say 1 vCPU with 2 GB), monitor the running VM for a while and then possibly expand the number of vCPUs or the amount of RAm assigned. • SQL Server running in a 2 vCPU virtual machine performed at 92 percent of a physical system booted with 2 CPUs. A good rule of thumb is, when sizing your VM, if the CPU utilization in the guest is on average below 20% at all times, reduce the number of vCPUs. Click the Options tab and choose Advanced. That is, plan a pilot that uses 8 to 10 virtual machines per core. Press the Ctrl + Shift + Esc keys simultaneously to open the Task Manager. NUMA. By default, vSphere manages the vCPU configuration and vNUMA topology automatically. If workloads are CPU-intensive, the vCPU-to-core ratio will need to be smaller; if workloads are not CPU. VMware uses the terms virtual CPU (vCPU) and physical CPU (pCPU) to distinguish between the processors within the VM and the underlying physical processor cores. vmdk (s) for data and another for logs. CPU virtualization adds varying amounts of overhead depending on the percentage of the virtual machine’s workload that can be run on the physical processor as is and the cost of virtualizing the remainder of the workload. 11-20-2021 04:45 AM. This also degrades performance of the VM. Upper limit for this virtual machine’s CPU allocation. Two vCPUs will be two cores or sockets, depending on how you configure it inside the guest, and will. The maximum CPU count depends on various factors, including the version of VMware Workstation, the host system’s hardware capabilities, and the selected CPU. That said, unless you set the CPU affinity of the emulator thread to one or more specific physical CPU core, the host OS scheduler may periodically migrate the thread to a different core every few seconds, much like any other process. min: The minimum number of virtual CPUs in a virtual machine that are required to generate a virtual NUMA topology. what is the current resources usage for this dual quad core physical? is it running at 90% cpu usage or 100% cpu usage or is it more like 40% or 20% cpu usage? you might find 4 vcpu virtual would work just as well, just because a server is dual quad core doesn't always mean the machine actually uses them all, all the time, that is the. Vcpu/Cpu Datacenter Sizing Calculator. 1. Without knowing other information like memory network capacity, processor usage etc. On the CPU side we would like to try and find out how much other people oversubscribe on there CPU's. Now we are setting the CPU reservation to 4*2500 = 10000 (remember, together with latency sensitivity high and so on). Adding this detail for the forum users who might find it helpful. Under the Core per Socket field, enter the total number of cores you would like to allocate to a socket. Go to the Performance tab and select CPU from the left column. VMware vCenter. by the number of virtual processors (vCPUs) on the server. The average virtual machine profile is: 4 vCPU and 4GB to 18GB RAM. Under Scheduling Affinity, select physical processor affinity for the virtual machine. vmdk on a different LUN to spread activity across multiple spindles. 3 physical CPU. 00. cpu. First of all, you need to start with the underlying hardware, CPU and memory. A high %RDY time (use 20 percent as the starting point) may indicate the VM is under resource contention. There have been some recent reports from users observing performance issues when running VMware Workstation on Windows 11 along with using recent Intel. Virtual servers / VMs - provide the total number of VMs and the total number of allocated vCPUs if any of the cost items are. 2) Yes there is no problem using Converter 4. Total amount of CPU resources available in the cluster. A Hyper-V vCPU is not a 1-to-1 mapping of a physical core. CPU Summation. To start with Physical component. To calculate virtual machine CPUs within the vSphere Client, multiply the number of sockets selected by. Here you can see that %RDY is somewhat high for a fairly unused environment. The reservation is expressed in MHz or GHz. If the VM is at 100% CPU utilization all the time, up the vCPU count. ESX server provides vCPUs for VM nodes. That is, the license will cover CPUs with up to 32 physical cores. e there are 112 vCPUs allocated. It is recommendable to leave 10% or more room for CPU bursts. 0 GHz. vSphere Cluster Calculator. You can configure virtual machines with one or more virtual processors, each with its own set of registers and control structures. . Subject to a minimum of 8 cores per processor and sixteen cores per host. 2) If you have an allocation pool with 12 GHz CPU allocation and a CPU speed of 1 GHz, the customer can use 12 vCPUs (12 * 1 GHz). Determining Host CPU and Memory Requirements. So setting a reservation will help improve performance for the VM you set it on, but will not “solve” CPU ready issues caused by “oversized” VMs, or by too high an overcommitment ratio of CPU. It is recommended to start with 1:1 vCPU-to-pCPU ratio, and then scale up the number of vCPUs while assessing. On the Virtual Hardware tab, expand CPU, and allocate the CPU capacity for the virtual machine. CORE = Logical Processor in physical chipset. For example, my lab has dual-socket ESXi host configurations, and each. Administering CPU Resources in vSphere. 0GHz turbo boost. In the above case, you can provide all cores to more than one VMs. VMware refers to CPU as pCPU and vCPU. 7GHz base clock and a 5. Unfortunately, Converter will take the number of physical cpus, and setup your VM with that number of vCPUs. Don’t assign an odd number of vCPUs when the size of your virtual machine, measured by vCPU count or configured memory, exceeds a physical NUMA node. Browse to the host in the vSphere Client. 5:1 or 2:1. 6. Total amount of CPU resources available in the cluster. Multiple vCPU’s, the hypervisor CPU scheduler must wait for physical CPU’s to become available Over allocation could result in poor performance. Google: For the n1 series of machine types, a vCPU is implemented as a single hardware hyper. For CPU's it isn't a 1 to 1 ratio for physical to virtual. Press c for the CPU view. For example, if a four-CPU host is running a virtual machine with two CPUs, and the usage is 50%, the host is using two CPUs completely. + (Average RDY Core 3) Because ESXi assign CPU resources to each machine when CPU cores available for all machines' cores, machine has 4 cores, so it has to wait for 4 core of physical cpu. 625 % per vCPU. Configuring Multicore Virtual CPUs. 5 to show CPU Ready. Sizing the physical environment. 1 Physical and Virtual CPUs VMware uses the terms virtual CPU (vCPU) and physical CPU (pCPU) to distinguish between the processors within the VM and the underlying physical processor cores. pCPU) The number of logical cores if hyper-threading is enabled on the host: (# of Physical Processors i. The definition can definitely vary, for example AWS defines vCPU as:. Essjae explained it correctly in basically saying each vCPU is borrowing CPU time from the physical processors. In your case as you approach 48 vCPUs your host will start making more use of logical cores (Hyperthreading) and you'll be moving into "over-provisioned" territory. For example, "0,2-4,7" would indicate processors 0, 2, 3, 4 and 7. For example, 5% of total ready reported in vSphere for an 8 vCPU virtual machine has the average of 0. The maximum CPU limit for a DRS cluster is the sum of numVMCPUs * GHzPerHostCore for. Share. So, where it had 0 CPU ready with a pair of vCPUs, even at 80%+ use, you could have a high percentage of CPU ready when going to 4 vCPUs on the same VM, with the use. This issue occurs when CPU reservation set on the virtual machine exceeds the physical CPU core capacity for the available ESXi hosts. ESXi Host CPU and CPU Overcommitment. Upper limit for this virtual machine’s CPU allocation. The total amount of clock cycles available for a VM is calculated as: (The number of logical sockets) x (The clock speed of the CPU) For example, if you configure a VM to use 2 vCPUs with 2 cores when you have a physical processor whose clock speed is 3. The first VM has 6 vCPUs, the second and third each have 4 vCPU's for a total of 14 vCPUs. also we need to install a third VM of Microsoft windows server 2019 for sage with 20vCPU (2 socket). In this case, VMware is very aware of hyperthreading and actively works to focus the CPU workload specifically on the physical cores. In the cloud environment, each host has number of sockets (physical CPU) with defined number of cores (E. When determining how many vCPUs to assign to an Exchange Server VM, always size assuming 1 vCPU = 1 physical core. Consider NUMA and ideally size VMs to. 0GHz and. 625 % per vCPU. If the CPU has more than 32 cores, additional CPU licenses are required. The Get Link button generates a URL for this page with all currently entered data and then shortens it using the Bitly service. So if we configure 8 vCPU for a VM, there must exist at least 8 pCPU in the host. If you have many / most VMs using vCPU lightly, you might be able to do 3:1 or 4:1. You should set cores per socket equal to vCPU until it gets larger than the cache domain, then it’s equal to the cache domain. For a typical Windows 7 implementation, use a minimum of 2 vCPUs per virtual machine to ensure a good user experience. We have a 2500 MHz CPU, with 2 CPUs, each one with 12 cores. g. So total for RAM we are thinking about. 2. AFAIK Hyper-threading (at least early versions) divided 1 CPU in 2 logical CPUs. : host with 8 logical cores, has 2. Press “c” for CPU view and you should see a column “ %RDY ” for CPU Ready. Note: An auto-growing . If you looked at ESXTOP, you would most likely notice that each HT was at 50% UTIL, and each PCPU (physical core) would be at 100% UTIL. Hi. 1 vCPU per VM. SOCKET = Physical hole where in one Processor can fit in. 7. If you have HT off, you should turn it on. Right-click a virtual machine in the inventory and select Edit Settings. If the workloads are CPU-intensive, the vCPU-to-core ratio will need to be smaller; if the workloads are not CPU-intensive, the vCPU-to-core ratio can be larger. To calculate virtual machine CPUs within the vSphere Client, multiply the number of sockets selected by the number of cores selected. This table provides the examples of socket determination based on CPU and Cores per Socket within the vSphere Web Client: The vCPU count is calculated by taking the number of processing threads per core and multiplying it by the number of cores and occupied CPU sockets. For the best performance, when you use manual affinity settings, VMware recommends that you include at least one additional physical CPU in the affinity setting to allow at least one of the. If your virtual machine still experiences performance issues, and if its kernel or HAL can handle switching to a single vCPU, lower the vCPU count to 1. Best way to allocate 8 vCPU to a VMUse the lowest value. in basic, 1 vCPU (which you configure for your VM) is mapped to 1 logical core. Hopefully this will clear things up in regards to your question - from Basic System Administration ESX Server 3. HI, Since Microsoft moved to per core licensing i. The CPU reservation for low latency VM is. One vCPU is equal to whatever the frequency of the physical CPU of the host on which the VM is running, regardless of how many cores there are. But performance problems can occur much earlier. One vCPU is equal to whatever the frequency of the physical CPU of the host on which the VM is running, regardless of how many cores there are. The calculator does not factor in the Non-Uniform Memory Access (NUMA) topology of a given hardware when making compute resource. For VPCs: 1 VPC equals 1 virtual CPU (vCPU); subject to the “lower of” rule above. A vCPU, on the other hand, is a software-based variant of a computer. Use the Number of virtual processor drop-down to lower the vCPU count by 1. 2x vCPU VM should not be. VM totalmhz = 2 vCPUs * 3000 MHz = 6000 MHz. Core,Logical CPU,vCPU Explained. This value is expressed in MHz or GHz. We have an ESXi Host, running a single VM that we need to optimize the CPU performance. Unfortunately I have seen this sometimes referenced as VM/core and other times. However, it is possible to assign more vCPUs than you have cores. 1 Solution schepp Leadership 07-20-2012 03:31 AM Hi. The total CPU sockets per host 3. I choosed to run 4 threads on 2 vCPU in windows VM. 50 : 1 :As an informal initial sizing approach, to start, assume that each virtual machine requires 1/8 to 1/10 of a CPU core as the minimum guaranteed compute power. It is recommended to start with 1:1 vCPU-to-pCPU ratio, and then scale up the number of vCPUs while assessing performance. CPU: vCPU Allocation % for 1 vCPU per Core: Metric: Disabled OOTB. The available CPU resources in the parent resource pool are insufficent for the operation. e. A good rule of thumb for a VDI pilot is that you should start out with each virtual machine defined by using 1/8 per vCPU of a CPU core at minimum. Put simply, the vCPU:pCore ratio assumes the N+1 host is not in the cluster which is how I personally size environments, especially for business critical. In reality the vCPU count is determined by the manufacturer - it is the number of processing threads that chipset offers per core. pCPU) X (2 cores) = # Virtual Processors (vCPU) Total CPU resources required for virtual machines at peak: The number of cores and threads of an Intel processor can be found in the Intel's Technical Specifications website by searching by processor number. For each group the tool calculates the Total cost per item and the Grand Total values. 6% of the total with one VM getting 66. One or more vCPUs are assigned to every Virtual Machine (VM) within a cloud environment. CPU virtualization adds varying amounts of overhead depending on the percentage of the virtual machine’s workload that can be run on the physical processor as is and the cost of virtualizing the remainder of. For hosts with Hyperthreading activated, the partner hyperthread has exclusive affinity to an idle world. Reservation Specifies the guaranteed minimum allocation for a virtual machine. This section provides guidance regarding CPU considerations in VMware VMware Cloud on AWS hosts. pCPU) The number of logical cores if hyper-threading is enabled on the host: (# of Physical Processors i. 1. 1 Calculate Bandwidth for vSphere Replication. There are only 4 execution resources available. - KVM: Physical CPU cannot be modified. and basing it on purely vCPU then 8 would be minimum but would give little room for moving machines around for patching ESXi, covering off high CPU workloads or providing resilience for potential hardware failures, I would recommend a minimum n+1 so 9 hosts. Hello @Shield07. + (Average RDY Core 3) Because ESXi assign CPU resources to each machine when CPU cores available for all machines' cores, machine has 4 cores, so it has to wait for 4 core of physical cpu. Some operating systems will have a maximum on number of vCPUs. To start with Physical component. If not known leave as Default. used exceed wall clock time due to Turbo Boost, or can see. This is very similar to how a mainframe works. Otherwise there is no other "Direct Passthrough" you can do -everything has to undergo ESXi's internal scheduler. The formula is: 1 (processor) * 2 (core) * 2 (threads) = 4; so, I could create a virtual machine with maximum 4 vCPU. A general estimation is that 1 vCPU = 1 Physical CPU Core. CPU usage is the average CPU utilization over all available virtual CPUs in the virtual machine. Right-click a virtual machine in the inventory and select Edit Settings. Answer. vcpu. Sorted by: 1. For instance, VMWare ESXi is hyperthreading aware, so it knows which "cores" are hyperthreading cores and which are "real". Ready (%RDY) - % time a vCPU was ready to be scheduled on a physical processor but couldn’t due to processor contention. I wouldn't hesitate to run 16 or even 32 VM's with single cores on a 8 core physical machine. Therefore, the formula for calculating the vCPU count is: (Threads x Cores) x Physical CPU Number = Number of vCPUs. On top of that, I recommend that you reserve at least one CPU core for the host operating system. This is documented in Hardware Features Available with Virtual Machine Compatibility Settings under: "Maximum number of cores (virtual CPUs) per socket". I am trying to understand vCPU concept in VMware. Second option is to use Prims PRO - Planning feature, add the new scenario and add existing workload or new. This can cause lag on the VM if other VMs are using the host CPU at the time. For the 55xx or newer CPU models, enabling HyperThreading will make a noticable difference. 5K user OVAs" since those are 2 vCPU each. thanks to everyone !You can do this by configuring VM reservations and/or limiting host memory overcommitment. VMware vSphere enables you to consolidate multiple workloads in the form of virtual machines on a single physical host. x support a maximum of 64 vCPUs per virtual socket. With this change, VMware is still using the per-CPU licensing model, but we will require one license for any software offering that we license on a per-CPU basis, for up to 32 physical cores. For example, if the physical host contains a single 10-core CPU package, do not assigned more than 10 vCPU to the Exchange Server VM. For example, if you assume 8 virtual machines per core and have a 2-socket 8-core ESXi host, you can host 128. AWS: Each vCPU is a thread of a CPU core, except for. A i7-980X has similar CPU power. As a result, a Windows host sees 2 CPUs, each one having about 50% of total CPU power. 1. It is possible for a VM to get 'stuck' on a single. Unfortunately I have seen this sometimes referenced as VM/core and other times. Basically, when you start adding more vCPU's to a VM than it actually needs, or will use, the CPU Ready stat will increase. The calculator is designed to be conservative and show information assuming the resources (CPU/RAM) required for the configured availability level are removed from the calculation. Average vCPU MHz – Average CPU utilization per desktop. For a low latency VM without vHT, each vCPU of the VM has exclusively affinity to a thread of the physical core. Towards 96 vCPUs you will be well into that territory and the. Total. Ghz per Core 4. For example, if a host has 128 logical CPUs, you can configure the virtual machine for 128 virtual CPUs. Virtual machines can not have more virtual CPUs than the actual number of logical CPUs on. (ESXI Installed). pCPU available on a host: (# of Processor Sockets) X (# of Cores) = # of Physical Processors (i. Yes, you can reserve the affinitized CPU to be exclusively used by that VM by selecting "HyperThreaded Sharing" option to "None" while on the CPU Affinity settings screen. In VMs, the operating system (OS) layer does not link directly to the physical hardware layer. The math is rather straight forward. 5% of single-core cpu-time. Select CPU and view the Usage % metric. Server Virtualization Calculator - estimates. vcpu. However, this is not entirely correct, as the vCPU is made up of time slots across all available physical cores, so in general 1vCPU is actually more powerful than a single core, especially if the physical CPUs have 8 cores. For every CPU cycle it always waits until there is a physical core available for each virtual CPU on a VM. Based on design, VMware ESXi can handle the CPU oversubscription (request of vCPU more than. Virtual socket —Represents a virtualized physical CPU and can be configured with one or more virtual cores. Table 2. I am trying to understand vCPU concept in VMware. The general rule of thumb is: start with 1 CPU and see if performance is acceptable. pCPU) The number of logical cores if hyper-threading is enabled on the host: (# of Physical Processors i. So forget about hyperthreading. 4Ghz) and the virtual version now has 2 vCPUs (The ESXI host has 2. On the Virtual Hardware tab, expand CPU, and allocate the CPU capacity for the virtual machine. Example: This table outlines. vCPUs run on pCPUs and by default, virtual machines are allocated one vCPU each. When running with lower CPU core frequency, %USED can be smaller than %RUN. Actually, there is not direct relationship between physical and vCPUs. SOCKET = Physical hole where in one Processor can fit in. Adding more vCPUs depends on the number of CPU cores and the number of timeslots, which are periods of times the. min . Determining this ratio will depend on the CPU utilization of the workloads. What hyperthreading does is present each core as two logical cores to your system. The calculator will then output the. Without knowing other information like memory network capacity, processor usage etc. Does it mean the sum of the VM's CPU can not exceed the number of the. When determining how many vCPUs to assign to an Exchange Server VM, always size assuming 1 vCPU = 1 physical core. 4. How does VMware handle. g. Otherwise there is no other "Direct Passthrough" you can do -everything has to undergo ESXi's internal scheduler. The description of the config field in Edit Settings is as follows: Hyperthreading Status: Active. Total number of VMs 7. As an informal initial sizing approach, to start, assume that each virtual machine requires 1/8 to 1/10 of a CPU core as the minimum guaranteed compute power. These are advanced settings designed to help workloads that are cache-intensive, but not CPU intensive. However, VMware have an add-on software module named Virtual SMP (symmetric multi-processing) that. If you have many more VMs on that host that can lead to a high CPU ready time and a very slow VM. For CPU's it isn't a 1 to 1 ratio for physical to virtual. Percentage of physical CPU core cycles used by the resource pool, virtual machine, or world. Scenarios where one host is not available because of failure or maintenance. You configure how the virtual CPUs are assigned in terms of cores and cores per socket. Click CPUs. Does this seems correct? pCPU Calculation (# Processor Sockets) X (# Cores/Processor) = # Physical Processors (pCPU) 2 x 20 = 40 pCPU vCPU Calculation (# pCPU) X (2 threads/physical processor. The exception to this would be when the guest OS and application is trying to schedule more CPU time than a single CPU core in the physical host can present (i. RAM - memory capacity allocated to a VM. Examples of this include a uniprocessor virtual machine with affinity to a single CPU or a two-way SMP virtual machine with affinity to only two CPUs. Sorted by: 3. And of course times the number of occupied sockets. Instead of physical processor-based licensing, it was decided that core-based is licensing is a more reliable and versatile metric to calculate the computing power irrespective of the fact that. 08-05-2008 08:45 AM.