Note that first use after a storage upgrade is slow

[jphenow]

What this gets us

People who upgrade a Sprite in place to the new storage find that their first commands, file reads and app requests are slow afterwards. The page only warned about a slow first start, so the later slowness looked like something had gone wrong. Now the page tells them to expect it and that it passes.

Approach

The intro to "Upgrading in place" now covers both slow phases: the disk copy during the first start, and the slower first use while the new storage loads data it hasn't cached yet. The verification steps now open with a one-line reminder, since that's where people will notice it.

Verify by hand

Read the "Upgrading in place" section on the preview and check that the two mentions agree with each other.

Calls worth a second opinion

• The duration is deliberately vague ("varies from Sprite to Sprite"). It depends on how much data the Sprite has and what gets accessed, so "depends on your data size" would only be partly true.
• The page doesn't explain the mechanism (cold extent cache, metadata warm-up). Customers can't act on those details.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
fly-io	🟢 Ready	View Preview	Oct 12, 2026, 2:33 PM

💡 Tip: Enable Automations to automatically generate PRs for you.