> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/fpt-gpu-cloud/high-performance-storage.md).
# High-performance Storage
## What is High-Performance Storage?
**File Storage—High Performance (HPS)** is a fully managed service that delivers **cost-efficient, high-performance, and scalable storage** for **GPU compute workloads**. It is designed to support demanding use cases such as **AI/ML training**, **high-performance computing (HPC)**, and **video rendering**, where multiple compute instances need simultaneous access to shared data with low latency and high throughput.
**Powered by VAST Data and DDN Storage**, two of the leading high-performance file system technologies optimized for **NVIDIA GPU clusters**, HPS provides exceptional performance—offering **throughput of up to hundreds of gigabytes per second** and **tens of thousands of IOPS** to meet the needs of the most data-intensive workloads.
## How Does It Work?
Mount **HPS** to **GPU Bare Metal** and **GPU Virtual Machine** services via the compute network (subnet) for seamless integration with your GPU workloads.
## Why High-performance Storage?
* **Highly Performant and Scalable:** Achieve hundreds of GB/s throughput and thousands of IOPS for demanding workloads.
* **Seamless S3 Integration:** Easily access and transfer data from other S3 buckets with the S3 gateway support.
* **Simple and Fully Managed:** Launch and manage HPS in a couple of hours, with no need for hardware provisioning or ongoing maintenance.
---
# 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://ai-docs.fptcloud.com/fpt-gpu-cloud/high-performance-storage.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.