이 페이지는 아직 한국어로 번역되지 않아 영어로 보여 드립니다.
A Drive is a disk of your project that lives on after the sandboxes that use it. Inside a sandbox it is a block device with its own ext4 file system, mounted at a path you choose, and its blocks are on the machine’s own NVMe disk. One sandbox has it at a time, read-write. When that sandbox goes, the Drive keeps what it holds, for the next sandbox.
As a Drive is written, it is copied into its region’s object store. So a sandbox on any machine of the region can mount it: if another machine held it last, it is brought over first, block by block as they are read. A sandbox of another region mounts it too, where that region’s machines read this one’s object store: its blocks come from its home region as they are read, and its home follows it there after an hour (across regions).
When to use Drive
- A database or a queue: a Cube with a Drive has one instance, which keeps its data across deploys and restarts.
- An agent’s workspace that outlives its sandbox: mount the same Drive in the next sandbox.
- One disk per user or session: each keyed instance of a Cube gets a Drive of its own.
- Large working data that a sandbox’s own disk should not hold.
- One data set for many readers: mount a snapshot of a Drive read-only in any number of sandboxes at once.
- A copy to try something on: fork a Drive, and delete the fork when you are done.
For a file system that several sandboxes mount at once, see shared volumes.
How it works
- Make.
POST /v1/drives(glac drives create) with a name, a size and a region. Only what is written takes space and is billed. - Mount. Give it to a new sandbox (
driveswhen you make it), to a running one (POST /v1/sandboxes/{id}/drives), or to a Cube’s version. - Keep. Unmount it, or delete the sandbox: the Drive stays with what it holds, in its region, until you delete it.
- Snapshot.
POST /v1/drives/{id}/snapshots(glac drives snapshots create data) keeps the Drive as it is now, without copying it. Restore the Drive to a snapshot, fork a new Drive from it, or mount it read-only: see snapshots and forks.
What it costs
| 과금 항목 | 가격 | 무료(하루 할당량) | 유료(월 포함 사용량) |
|---|---|---|---|
| 드라이브의 데이터(기록된 바이트 기준, 전부 계층형 스토리지에 보관) | GB-월당 $0.02 | 잠든 인스턴스와 스냅샷을 포함해 데이터 합계 15 GB | 잠든 인스턴스와 스냅샷을 포함해 데이터 20 GB-월 |
| 드라이브의 NVMe 캐시(설정한 크기만큼) | GB-월당 $0.06 | 합계 15 GB | 20 GB-월 |
| 드라이브 쓰기와 읽기 | 요금 없음 |
A Drive is billed by its data and its NVMe cache. Its data is counted by the bytes written to it and not trimmed away, not by its size, hour by hour, all of it kept in tiered storage; its cache is the part of it kept on the machine’s NVMe, the size you set: all of it for local speed, none for the lowest price, or a balance between. Writing and reading cost nothing. Free’s data is shared with sleeping sandboxes and snapshots. A snapshot of a Drive is billed for what it keeps alone, at the same price: see snapshots and forks and pricing and plans.
Limits of each plan
| 무료 | 유료 | |
|---|---|---|
| 프로젝트 하나의 드라이브와 볼륨 수 | 3 | 500 |
| 최대 드라이브 크기 | 10 GiB | 1 TiB |
| 프로젝트의 드라이브 전체 합계 | 15 GiB | 제한 없음 |
| 샌드박스 하나가 마운트하는 드라이브와 볼륨 수 | 8 | 8 |
The number of Drives on Paid is a soft limit: ask us to raise it. An enterprise account can be given Drives of up to 16 TiB. See the limits page.
Not there yet
- A Cube’s version mounts its Drives read-write only: read-only mounts of a snapshot are for sandboxes.
Next
- Quickstart: make a Drive, write to it from one sandbox, read it from the next.
- How Drives work: mounting, one writer, where a Drive is, what is billed.
- Snapshots and forks: keep a Drive as it is, restore it, fork it, mount it read-only in many sandboxes.
- Shared volumes and backups: file systems several sandboxes mount at once.