> For the complete documentation index, see [llms.txt](https://docs.lagrangedao.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lagrangedao.org/spaces/space-settings/instance-type.md).
# Instance Type
### Instance Type Naming Convention
Instance types are named based on their family, generation, processor family, additional capabilities, and size.
* The first position of the instance type name indicates the instance family, for example `p`.
* The second position indicates the instance generation, for example `1`.
* The third position indicates the processor family, for example `a`.
* The remaining letters before the period indicate additional capabilities, such as instance store volumes.
* After the period (`.`) is the instance size, such as `small` or `4xlarge`.
#### **Instance families**
* **C** – Compute optimized
* **D** – Dense storage
* **F** – FPGA
* **G** – Graphics intensive
* **Hpc** – High performance computing
* **I** – Storage optimized
* **M** – General purpose
* **Mac** – macOS
* **P** – GPU accelerated
* **R** – Memory optimized
* **T** – Burstable performance
* **U** – High memory
* **VT** – Video transcoding
* **X** – Memory intensive
#### **Processor families**
* **a** – AMD processors
* **i** – Intel processors
#### **Additional capabilities**
* **d** – instance store volumes
* **e** – Extra storage or memory
* **z** – High performance
* **flex** – Flex instance
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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.lagrangedao.org/spaces/space-settings/instance-type.md?ask=
```
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.