From 16e2192d0d99823ea8ae5ae4003ec07a7150cef5 Mon Sep 17 00:00:00 2001 From: Michael Psomiadis Date: Mon, 5 Oct 2026 17:12:04 +1100 Subject: [PATCH] Update Machines rootfs I/O limits https://github.com/superfly/machines-meta/issues/65#issuecomment-5624827221 --- volumes/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/volumes/overview.mdx b/volumes/overview.mdx index 420c43ecd4..d3e78039b4 100644 --- a/volumes/overview.mdx +++ b/volumes/overview.mdx @@ -5,7 +5,7 @@ source_url: https://fly.io/docs/volumes/overview/ Illustration by Annie Ruygt of a filing cabinet -The root file systems of a Fly Machine are ephemeral and should only be used for temporary data, application code, and runtime files that can be rebuilt from scratch during deployments or restarts. The performance of these ephemeral disks are heavily limited regardless of the Machine type you choose, with the maximum of 2000 IOPs and 8MiB/s bandwidth. +The root file systems of a Fly Machine are ephemeral and should only be used for temporary data, application code, and runtime files that can be rebuilt from scratch during deployments or restarts. The performance of these ephemeral disks is limited based on machine type and size, the same as [Volumes](/volumes/overview#volume-limits). Fly Volumes are local persistent storage for [Fly Machines](/machines). You can access and write to a volume on a Machine just like a regular directory. Use volumes to store your database files, to save your app's state, such as configuration and session or user data, or for any information that needs to persist after deploy or restart. Maximum volume performance varies by Machine type and noted in [Volume limits](/volumes/overview#volume-limits)