# Launching a Virtual Machine

### Overview

YottaLabs provides an intuitive interface for launching virtual machines with powerful GPU resources. Whether you're training machine learning models, running scientific simulations, or performing data analysis, this platform makes it easy to configure the exact resources you need.

***

<figure><img src="/files/LnepUE8qdxEocKVmp4BM" alt=""><figcaption></figcaption></figure>

#### 1. Region Selector

<figure><img src="/files/k5w2YFwgVT02Vnbxa0tM" alt=""><figcaption></figcaption></figure>

**What it does:** Selects the geographic location where your virtual machine will be hosted.

**Why it matters:**

* **Latency**: Choose a region close to you for faster response times
* **Availability**: Different regions may have different GPU availability

***

#### 2. Network Storage

<figure><img src="/files/4LrSFRklrGsBej9aZDKf" alt="" width="371"><figcaption></figcaption></figure>

**What it does:** Configures persistent network-attached storage for your virtual machine.

**Storage types typically include:**

* **Standard SSD**: Good for general purpose workloads
* **High-performance SSD**: For I/O intensive applications
* **Archive storage**: For infrequently accessed data

**Why it matters:**&#x59;our instance's local storage is ephemeral (lost when instance stops)!

***

#### 3. VRAM Slider

<figure><img src="/files/lprEhe2j00BdiJEwfa1q" alt="" width="435"><figcaption></figcaption></figure>

**What it does:** Filters instance types based on GPU memory (VRAM) requirements.

**Why it matters:**

* Different models require different amounts of GPU memory
* Training large language models needs 40GB+ VRAM
* Small computer vision models might only need 8-16GB

**Example use cases:**

* **1-8 GB**: Small datasets, inference, light training
* **16-24 GB**: Medium neural networks, most computer vision tasks
* **40-80 GB**: Large language models, high-resolution image processing
* **80+ GB**: Multi-GPU training, extremely large models

***

#### 4. RAM Slider

**What it does:** Filters instance types based on system RAM .

{% hint style="info" %}
**VRAM vs RAM**

RAM is the CPU's general-purpose workspace for running the OS and apps, while VRAM is the GPU's high-speed dedicated memory used exclusively for rendering textures, 3D graphics, and video frames. Essentially, RAM manages the "logic" of your computer, whereas VRAM handles the "visuals."

**For deep learning, a good rule of thumb is 2-4x your VRAM in system RAM.**
{% endhint %}

**Why it matters:**

* Data preprocessing often happens in system RAM
* Large datasets need to fit in memory
* Some applications are RAM-intensive even without GPUs

***

#### Provider Selection

Choose different GPU providers:

***

### GPU Configuration

#### Multi-GPU Selection Buttons

* Not all code can utilize multiple GPUs without modification
* You'll need to implement data parallelism or model parallelism
* PyTorch: Use `DataParallel` or `DistributedDataParallel`
* TensorFlow: Use distribution strategies
* Monitor GPU utilization - don't pay for GPUs you're not using!

***

#### Operating System Selection

**What it does:** Selects the operating system for your virtual machine.

**Ubuntu 22.04 LTS**: Long-term support, most stabled configurations

<figure><img src="/files/TC12IXOidpOj1YB4PWHD" alt=""><figcaption></figcaption></figure>

**Ubuntu 22.04 LTS** (shown above):

* **LTS** = Long Term Support (5 years of updates)
* Well-supported by AI/ML tools
* Most documentation assumes Ubuntu
* Native NVIDIA CUDA support

***


---

# 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.yottalabs.ai/products/virtual-machines/launching-a-virtual-machine.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.
