Volume Scheduler

You provisioned 10,000 IOPS on a volume because your application needs it during business hours. That's 10 hours a day, five days a week. The other 118 hours? The volume is still running at 10,000 IOPS. Nobody is reading. Nobody is writing. You're paying for peak performance on an idle disk.

Outscale charges for IOPS. The higher the tier, the higher the cost. A volume sitting at maximum IOPS overnight isn't "ready for tomorrow" — it's wasting money tonight.

What it does

Volume Scheduler adjusts IOPS on your Outscale volumes based on a schedule. High IOPS during work hours when your application needs the throughput. Baseline IOPS overnight and weekends when the disk is idle.

It's the same principle as instance scheduling — but for storage performance instead of compute. And just like instance scheduling, the savings are proportional to how much time your workload is actually active.

The scheduler supports planned overrides too. Running a batch job this Saturday? Override the schedule for that volume, keep it at peak IOPS for the duration, and let it drop back automatically when the job's done. One-time or recurring — you choose.

How it works

Pick the volumes you want to manage. Define two IOPS levels: the "active" tier for business hours and the "idle" tier for off-hours. Set the schedule — days, start time, end time, timezone.

The scheduler handles the transitions. At your start time, it bumps IOPS to the active level. At your end time, it drops them to idle. Every change is logged in the audit trail with the exact IOPS values — before and after.

For volumes attached to scheduled instances, this works in concert with the Instance Scheduler. The VM stops, the IOPS drop. The VM starts, the IOPS restore. No manual coordination needed.

Planned overrides let you handle exceptions without breaking the base schedule. A one-time override for a Saturday deployment. A recurring override for a weekly batch window. The override takes priority during its window, then the normal schedule resumes automatically.

Why it matters

IOPS costs are sneaky. They don't show up as a big line item — they're distributed across dozens of volumes, each one a small amount. But add them up and you're looking at hundreds or thousands of euros per month in IOPS you're paying for but not using.

Volume scheduling captures that waste automatically. No manual intervention, no "remember to scale down the volumes before you leave." The schedule runs, the IOPS adjust, the savings accumulate.

For teams already using Instance Scheduler, Volume Scheduler is the natural next step. You've stopped paying for idle compute. Now stop paying for idle storage performance too.

Cut your storage costs while you sleep. Start your free trial on Vextnd.