Dedicated Core Servers

dedicated core servers that you create in the dcd https //docs ionos com/cloud/support/general information/glossary of terms#dcd are provisioned and hosted in one of 's physical data centers dedicated core servers behave exactly like physical servers https //docs ionos com/cloud/compute services/compute engine/dedicated core#availability zones they can be configured and managed with your choice of the operating system for more information, see configure a dedicated core server https //docs ionos com/cloud/set up ionos cloud/get started/configure data center#configure a dedicated core server boot options for each server, you can select to boot from a virtual cd rom/dvd drive or a storage device ( hdd https //docs ionos com/cloud/support/general information/glossary of terms#hdd or ssd https //docs ionos com/cloud/support/general information/glossary of terms#ssd ) using any operating system on the platform the only requirement is the use of kvm virtio drivers https //docs ionos com/cloud/backup and storage/block storage/how tos/install windows virtio drivers provides a number of ready to boot images https //docs ionos com/cloud/backup and storage/images snapshots/public images with multiple versions of microsoft windows and different linux distributions, including red hat enterprise linux availability zones secure your data, enhance reliability, and set up high availability scenarios by deploying your dedicated core servers and storage devices across multiple availability zones https //docs ionos com/cloud/support/general information/glossary of terms#availability zone assigning different availability zones ensures that servers or storage devices reside on separate physical resources at for example, a server or a storage device assigned to availability zone 1 resides on a different resource than a server or storage device assigned to availability zone 2 you have the following availability zone options zone 1 zone 2 a auto (default; our system automatically assigns an availability zone on provisioning) nic multi queue to significantly enhance a virtual machine's (vm's) https //docs ionos com/cloud/support/general information/glossary of terms#virtual machine vm network performance, nic multi queue https //docs ionos com/cloud/network services/vdc networking/nic multi queue distributes network traffic by assigning multiple queues to the vm based on its cpu cores, which prevents input or output (i/o) bottlenecks and reduces latency this results in improved throughput and is critical for applications that require high network bandwidth, such as databases and high performance computing workloads for more information on enabling it for your vm, see enable nic multi queue https //docs ionos com/cloud/network services/vdc networking/nic multi queue#nic multi queue live vertical scaling (lvs) if the capacity of your virtual data center no longer matches your requirements, you can still increase or decrease your resources after provisioning upscaling resources allows you to change the resources of a dedicated core server without restarting it, permitting you to add ram or nics https //docs ionos com/cloud/support/general information/glossary of terms#nic ("hot plug") to it while it is running this change allows you to react to peak loads quickly without compromising performance warning ram hotplugging for a vm is automatically disabled when the ram size exceeds 240 gb this leads to the vm restarting every time the ram is increased beyond this limit, disabling live vertical scaling after uploading, you can define the properties of your images before applying them to new storage volumes the settings must be supported by the image, otherwise, they will not work as expected after provisioning, you can change the settings directly on the storage device, which will require a restart of the server the types of resources that you can scale without rebooting will depend on the operating system of your virtual machines (vms) https //docs ionos com/cloud/compute services/compute engine/dedicated core#availability zones since kernel 2 6 25, linux has lvo modules installed by default, but you may have to activate them manually depending on the derivative virtio https //docs ionos com/cloud/support/general information/glossary of terms#virtio drivers are optimized for virtual environments and provide direct access to underlying hardware for images, the supported properties are already preset without restarting the dedicated core server, its resources can be scaled as follows upscaling cpu, ram, nics, storage volumes downscaling nics, storage volumes scaling up is the increase or speed up of a component to handle a larger load the goal is to increase the number of resources that support an application to achieve or maintain accurate performance scaling down means reducing system resources, irrespective of whether you have used the scaling up approach without restarting the dedicated core server, only upscaling is possible limitations cpu types dedicated core server configurations are subject to the following limitations, by cpu type amd cpu components minimum maximum cores 1 core 62 cores ram 0,25 gb ram 230 gb ram nics and storage 0 pci connectors 24 pci connectors cd rom 0 cd roms 2 cd roms intel® cpu components minimum maximum cores 1 core 62 cores ram 0,25 gb ram 230 gb ram nics and storage 0 pci connectors 24 pci connectors cd rom 0 cd roms 2 cd roms note additional ram sizes are available on request to increase the ram size, contact your sales representative or support https //docs ionos com/cloud/support/general information/contact information a single physical processor core using simultaneous multithreading (smt) is recognized by the operating system of your dedicated core server as two distinct "logical cores", which allows it to process separate threads concurrently ram sizes because the working memory (ram) size cannot be processed during the initial configuration, newly provisioned servers with more than 8 gb of ram may not start successfully when created from windows images live vertical scaling linux supports the entire scope of live vertical scaling, whereas windows is limited to cpu scaling furthermore, it is impossible to use lvs to reduce storage size after provisioning