Per socket
Catalog row in Vendor License Metrics · Cited
- Unit
- Socket
- Aliases
- CPU Socket; Processor Socket; Per socket license; XenServer CPU socket
- Definition
- Per socket licenses are consumed based on the number of CPU sockets. Cores are not counted. For example: If a computer with two CPU sockets has only one CPU then only one license is consumed. If a computer with two sockets has two CPUs, each with a quad core, then two licenses are used. Citrix Hypervisor uses per socket licenses.
- Counting rules
- Per socket licenses are consumed based on the number of CPU sockets. Cores are not counted. Example: a computer with two CPU sockets and only one CPU consumes one license; two sockets with two CPUs consume two licenses. Product.html Hypervisor footnote: an individual populated CPU socket; unpopulated CPU sockets do not require a license. App-delivery footnote on the same Product specific terms page says sockets need licenses regardless of whether or not the socket contains a CPU; the two footnotes conflict. The Hypervisor-specific populated-socket footnote is the one specific to XenServer. UHMC/Platform 10,000 included sockets is a bundle entitlement, not a per-User ratio.
- Floors / minimums
- UHMC / Citrix Platform / Private Cloud notes: 10,000 XenServer CPU socket licenses included. Conflict on product.html: Hypervisor footnote (populated sockets only) vs app-delivery footnote (sockets regardless of CPU) — unpublished resolution.
- Applies to products
- Citrix Hypervisor
- Applies to editions
- Enterprise
- Standard
- Related metrics
- Product category