# Models, Zones & Operating System

Zenlayer virtual machines have three kinds of models with different configurations. The table below displays the main parameters as reference.

## **Models**

Four types of specifications are supported:

* **Compute-optimized (Dedicated vCPU)**\
  Compute-optimized instances typically have a higher vCPU-to-memory ratio, such as 1 vCPU to 2 GB of RAM, making them well-suited for compute-intensive workloads.
* **General-purpose (Dedicated vCPU)**\
  General-purpose instances have a 1:4 vCPU-to-memory ratio, making them ideal for various workloads, including web servers, small databases, and development environments, that require moderate compute and memory resources.
* **Memory-optimized (Dedicated vCPU)**\
  Memory-optimized instances have a higher memory-to-vCPU ratio, such as 8GB of RAM per CPU, making them well-suited for memory-intensive workloads that require large amounts of memory, such as database management and high-performance computing.
* **Basic compute (Shared vCPU)**\
  Basic compute instances offer shared vCPU resources, making them a cost-effective option for running basic workloads that don't require a lot of computing power or memory, such as simple web applications and lightweight development environments.

The available types are shown in the following table.

<table><thead><tr><th width="185">Instance Model</th><th width="159">vCPU (Core)</th><th width="149">RAM (GB)</th><th>Bandwidth Cap (Gbps)</th></tr></thead><tbody><tr><td>c.1c2g</td><td>1</td><td>2</td><td>0.5</td></tr><tr><td>c.2c4g</td><td>2</td><td>4</td><td>1</td></tr><tr><td>c.4c8g</td><td>4</td><td>8</td><td>1.5</td></tr><tr><td>c.8c16g</td><td>8</td><td>16</td><td>2</td></tr><tr><td>c.12c24g</td><td>12</td><td>24</td><td>2.5</td></tr><tr><td>c.16c32g</td><td>16</td><td>32</td><td>3</td></tr><tr><td>c.24c48g</td><td>24</td><td>48</td><td>4.5</td></tr><tr><td>c.32c64g</td><td>32</td><td>64</td><td>6</td></tr><tr><td>c.64c128g</td><td>64</td><td>128</td><td>6</td></tr><tr><td>g.2c8g</td><td>2</td><td>8</td><td>1</td></tr><tr><td>g.4c16g</td><td>4</td><td>16</td><td>1.5</td></tr><tr><td>g.8c32g</td><td>8</td><td>32</td><td>2</td></tr><tr><td>g.16c64g</td><td>16</td><td>64</td><td>3</td></tr><tr><td>g.24c96g</td><td>24</td><td>96</td><td>4.5</td></tr><tr><td>g.32c128g</td><td>32</td><td>128</td><td>6</td></tr><tr><td>m.2c16g</td><td>2</td><td>16</td><td>1</td></tr><tr><td>m.4c32g</td><td>4</td><td>32</td><td>1.5</td></tr><tr><td>m.8c64g</td><td>8</td><td>64</td><td>2</td></tr><tr><td>m.16c128g</td><td>16</td><td>128</td><td>3</td></tr><tr><td>s.1c1g</td><td>1</td><td>1</td><td>0.5</td></tr><tr><td>s.1c2g</td><td>1</td><td>2</td><td>0.5</td></tr><tr><td>s.2c2g</td><td>2</td><td>2</td><td>0.5</td></tr><tr><td>s.2c4g</td><td>2</td><td>4</td><td>1</td></tr><tr><td>s.4c8g</td><td>4</td><td>8</td><td>1.5</td></tr><tr><td>s.8c16g</td><td>8</td><td>16</td><td>2</td></tr></tbody></table>

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">`c`</mark> <mark style="color:blue;">refers to vCPU and</mark> <mark style="color:blue;">`g`</mark> <mark style="color:blue;">refers to memory. For example, Compute-optimized 1c2g (c.1c2g) refers to 1 vCPU cores and 2 GB memory;</mark> <mark style="color:blue;">General-purpose 2c8g (g.2c8g)</mark> <mark style="color:blue;">refers to 1 vCPU cores and 2 GB memory.</mark>
* <mark style="color:blue;">The available models in each location vary depending on the inventory.</mark>
  {% endhint %}

## **Available Locations**

Virtual Machine instances are deployed by locations. Each location has its own power grid and network structure. Your instances in the same location can buildup private network by VPC.

| Region                 | City           |
| ---------------------- | -------------- |
| Americas               | Los Angeles    |
| Americas               | Mexico City    |
| Americas               | San Paulo      |
| Americas               | Washington D.C |
| Asia Pacific           | Hanoi          |
| Asia Pacific           | Hong Kong      |
| Asia Pacific           | Kolkata        |
| Asia Pacific           | Melbourne      |
| Asia Pacific           | Mumbai         |
| Asia Pacific           | New Delhi      |
| Asia Pacific           | Singapore      |
| Asia Pacific           | Taipei         |
| Asia Pacific           | Tokyo          |
| Europe and Middle East | Frankfurt      |
| Europe and Middle East | Istanbul       |
| Europe and Middle East | Jeddah         |
| Europe and Middle East | London         |
| Europe and Middle East | Paris          |
| Europe and Middle East | Riyadh         |
| Europe and Middle East | Zurich         |

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

<mark style="color:blue;">More locations will be added in the future.</mark>
{% endhint %}

## **Supported Operating System**

| OS      | Version              |
| ------- | -------------------- |
| CentOS  | centos 6.8 x86\_64   |
| CentOS  | centos 6.9 x86\_64   |
| CentOS  | centos 7.2 x86\_64   |
| CentOS  | centos 7.3 x86\_64   |
| CentOS  | centos 7.4 x86\_64   |
| CentOS  | centos 7.5 x86\_64   |
| CentOS  | centos 7.6 x86\_64   |
| CentOS  | centos 8.2 x86\_64   |
| Ubuntu  | ubuntu 14.04 x86\_64 |
| Ubuntu  | ubuntu 16.04 x86\_64 |
| Ubuntu  | ubuntu 18.04 x86\_64 |
| Ubuntu  | ubuntu 20.04 x86\_64 |
| Windows | windows 2008 x86\_64 |
| Windows | windows 2012 x86\_64 |
| Windows | windows 2016 x86\_64 |
| Windows | windows 2019 x86\_64 |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.console.zenlayer.com/welcome/virtual-machine/overview/models-zones-and-operating-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.