Getting Started with Dedicated CPUs

Traducciones al Español
Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

This guide will serve as a brief introduction into what a Dedicated CPU Linode is and how to add one to your Linode account. Review our Use Cases for Dedicated CPUs guide for more information about the tasks that work well on this instance type.

What is a Dedicated CPU Linode?

In contrast with a Shared Linode, which gives you access to shared virtual CPU cores, a Dedicated CPU Linode offers entire physical CPU cores that are accessible only by your instance. Because your cores will be isolated to your Linode, no other Linodes can schedule processes on them, so your instance will never have to wait for another process to complete its execution, and your software can run at peak speed and efficiency.

While a Shared Linode is a good fit for most use cases, a Dedicated CPU Linode is recommended for a number of workloads related to high, sustained CPU processing, including:

Deploying a Dedicated CPU Linode

  1. Log in to the Linode Cloud Manager.

  2. Click on the Create dropdown menu at the top left of the page, and select the Linode option.

  3. Select a Distribution, Marketplace App, or Image to deploy from.

    Use a StackScript to quickly deploy software platforms and system configuration options to your Linux distribution. You can read more about StackScripts and how they work in our Automating Deployments with StackScripts Guide.
  4. Choose the region where you would like your Linode to reside. If you’re not sure which to select, see our How to Choose a Data Center guide. You can also generate MTR reports for a deeper look at the network route between you and each of our data centers.

  5. At the top of the Linode Plan section, click on the Dedicated CPU tab and select the Dedicated CPU plan you would like to use.

  6. Enter a label for your new Linode under the Linode Label field.

  7. Enter a strong root password for your Linode in the Root Password field. This password must be provided when you log in to your Linode via SSH. The password must meet the complexity strength validation requirements for a strong password. Your root password can be used to perform any action on your server, so make it long, complex, and unique.

    You are not prompted to enter a root password if you are cloning another Linode or restoring from the Linode Backups service.
  8. Optionally, add an SSH key, Backups, or a Private IP address.

  9. Click the Create button when you have finished completing this form. You are redirected to the overview page for your new Linode. This page shows a progress bar which indicates when the Linode has been provisioned and is ready for use.

Next Steps

See our Creating a Compute Instance guide for help with connecting to your Linode for the first time and configuring the software on it. Then visit the Setting Up and Securing a Compute Instance guide for a collection of security best practices for your new Linode.

This page was originally published on

Your Feedback Is Important

Let us know if this guide was helpful to you.

Join the conversation.
Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our Support team or asking on our Community Site.
The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please update your Cookie Preferences on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.