> For the complete documentation index, see [llms.txt](https://docs.mithril.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mithril.ai/compute-and-storage/compute-overview.md).
# Compute overview
Infrastructure designed to maximize price-performance for your ML workloads
Mithril offers two core mechanisms for provisioning compute:
1. **Short-term reserved instances:** Reservations give you guaranteed access to interconnected nodes. Reserved instances are typically useful for large, preplanned workloads like training that need to run uninterrupted. You can reserve instances in advance for as little as 3 hours and for up to 2 weeks. Reserved instance pricing is adjusted gradually based on overall supply and demand.
2. **Spot instances:** Spot instances provide a more dynamic way to access compute. To use spot instances, you submit a limit-price order that specifies the *maximum* price per GPU-hour you are willing to pay. Whenever the spot price is *lower* than your limit price, your spot instances spin up.
## Provisioning compute
Making reservations
Reserve interconnected nodes for as little as 3 hours for preplanned workloads.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mithril.ai/compute-and-storage/compute-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
