Cloud servers with dedicated cores
A cloud server with dedicated cores is a cloud server with vCPUs that are tied to the threads of specific physical processor cores rather than switching between threads of different cores.
Dedicated cores guarantee that the cloud server uses processor resources without competing for computing power with other cloud servers. Such isolation:
- provides the cloud server with stable performance;
- protects the cloud server from hardware vulnerabilities (such as Spectre, Meltdown, and others) caused by other cloud servers on the same physical node.
Dedicated core configuration is available when creating a cloud server or when changing the cloud server configuration.
For a cloud server with dedicated cores, the Hyper-Threading (SMT) option is enabled by default. You can also configure mandatory resource placement on a single NUMA node.
Use cases
Suitable for high-load and performance-critical systems that require predictable and stable vCPU performance without the influence of other cloud servers:
- for running resource-intensive databases;
- for processing analytical tasks and tasks with high computational complexity;
- for running CI/CD servers;
- for hosting game servers and real-time applications requiring low latency;
- for deploying microservices and high-request-rate APIs;
- for ensuring stable monitoring and logging performance during high event rates.
Hyper-Threading
Hyper-Threading (SMT or Hyper-Threading) is a technology that allows a single physical processor core to process two threads simultaneously. In this case, each pair of vCPU of the cloud server corresponds to two threads of one physical processor core.
This technology improves performance for multi-threaded tasks, for example, when running web servers and enterprise applications, or for video rendering and processing. Learn more about the technology and its operating principles in the Servercore blog article What is Hyper-Threading.
On cloud servers with dedicated cores, Hyper-Threading (SMT) is enabled by default. It is not possible to enable Hyper-Threading (SMT) for cloud servers without dedicated cores.
For databases, high-performance computing (HPC) tasks, or software licensed by physical cores, we recommend testing system performance with the Hyper-Threading (SMT) option both enabled and disabled. If necessary, you can disable the option:
- for stable performance in single-threaded scenarios;
- for task isolation at the physical core level;
- for license compliance.
When you disable the Hyper-Threading (SMT) option, threads are disabled — each vCPU of the cloud server corresponds to a whole physical processor core. The number of vCPUs on the cloud server is halved.
For example, you create a cloud server with the Hyper-Threading (SMT) option enabled and 8 vCPUs. The cloud server will use 4 physical cores, each operating in Hyper-Threading (SMT) mode, which means it processes 2 threads. Thus, the cloud server has 8 vCPUs.
If you disable the Hyper-Threading (SMT) option, the number of vCPUs on the cloud server will be reduced to 4, which will correspond to the number of physical cores rather than the number of threads. The number of occupied physical cores will remain the same, so the cloud server cost will not change.
Before disabling Hyper-Threading (SMT), be sure to test application performance under load — some applications may run slower without Hyper-Threading (SMT).
Mandatory resource placement on a single NUMA node
NUMA (Non-Uniform Memory Access) is a multiprocessor system architecture. NUMA nodes are architectural units in multiprocessor systems, where a node includes one processor and local RAM, to which the processor within the node has fast access with low latency.
When resources are placed on a single NUMA node, the cloud server operates only within that node — it uses the processor cores and local memory tied to that node. This promotes minimal memory access latency.
You can enable mandatory resource placement on a single NUMA node when creating a cloud server or changing the cloud server configuration only for servers with dedicated cores and 4 or more vCPUs. You cannot enable mandatory resource placement on a single NUMA node for cloud servers without dedicated cores.
If it is not possible to place cloud server resources on a single NUMA node, the server will not be created.
Limitations
Cloud servers with dedicated cores are available only in pool segments ru-3b, ru-7a, ru-7b, and all segments of the multi-AZ pool ru-6.
Dedicated core configuration is available only in the Standard and HighFreq lines. You can view the list of fixed configuration flavors in these lines that support dedicated cores in the table List of fixed configuration flavors in all pools.
Cost
The cost of a cloud server with dedicated cores, the Hyper-Threading (SMT) option, and the mandatory placement on a single NUMA node option can be viewed at servercore.com.
The cost of a cloud server with dedicated cores does not change:
-
when the Hyper-Threading (SMT) option is enabled or disabled;
-
when the mandatory placement on a single NUMA node option is enabled or disabled.