EFS Performance Calculator
Model EFS bursting credits: baseline throughput, burst ceiling and how long the credit bucket lasts under load.
Inputs
Bursting mode earns 50 KiB/s of baseline for every GiB stored.
100 MiB/s minimum, then 100 MiB/s for every TiB stored.
Burst Runway
15.3 hours of burst before the credit bucket empties
Baseline Throughput
100.00MiB/s
Burst Throughput Ceiling
200.00MiB/s
Hours of Burst Available
15.3hours
Provisioned Throughput to Buy
80.00MiB/s
Provisioned Throughput Cost
$480.00
Step by step
Values used
Standard-tier data in the file system = 2,048 GiB; Baseline throughput earned per GiB = 50 KiB/s per GiB; Burst throughput per TiB = 100 MiB/s per TiB; Credit bucket size per TiB stored = 2.10 TiB per TiB; Sustained throughput the workload drives = 180 MiB/s; Provisioned throughput price = 6 USD per MiB/s-month
EFS Performance
baseline MiB/s = GiB x 50 KiB/s ÷ 1024; burst runway hours = credit bucket in MiB ÷ ((demand − baseline) x 3600).
Burst Runway
= 15.3 hours of burst before the credit bucket empties
Baseline Throughput
= 100.00 MiB/s
Burst Throughput Ceiling
= 200.00 MiB/s
Hours of Burst Available
= 15.3 hours
Provisioned Throughput to Buy
= 80.00 MiB/s
Provisioned Throughput Cost
= 480.00
How it works
In Bursting mode an EFS file system earns throughput from the bytes it stores: 50 KiB/s of baseline per GiB, with a credit bucket that lets it run far above that until the credits are gone. Any demand above baseline drains the bucket at exactly the excess rate, so a small file system driving heavy throughput has a runway measured in hours, then collapses to baseline. Buying only the excess as Provisioned Throughput is what turns that cliff into a flat, predictable rate — priced here from a user-supplied list price to confirm on the AWS EFS pricing page for your region. Almost every EFS performance incident is a drained credit bucket rather than a broken workload, and the runway figure tells you how many hours of a batch window you have before the file system throttles.
Formula
EFS Performance
baseline MiB/s = GiB x 50 KiB/s ÷ 1024; burst runway hours = credit bucket in MiB ÷ ((demand − baseline) x 3600).
- credit bucket
- MiB of burst credit held, sized from the TiB stored
- drain
- Demand above baseline, the rate credits are consumed
Frequently Asked Questions
How is EFS Performance calculated?
baseline MiB/s = GiB x 50 KiB/s ÷ 1024; burst runway hours = credit bucket in MiB ÷ ((demand − baseline) x 3600). In Bursting mode an EFS file system earns throughput from the bytes it stores: 50 KiB/s of baseline per GiB, with a credit bucket that lets it run far above that until the credits are gone. Any demand above baseline drains the bucket at exactly the excess rate, so a small file system driving heavy throughput has a runway measured in hours, then collapses to baseline. Buying only the excess as Provisioned Throughput is what turns that cliff into a flat, predictable rate — priced here from a user-supplied list price to confirm on the AWS EFS pricing page for your region.
Why does EFS Performance matter?
Almost every EFS performance incident is a drained credit bucket rather than a broken workload, and the runway figure tells you how many hours of a batch window you have before the file system throttles.
What values do I need to enter?
This calculator takes 6 inputs: Standard-tier data in the file system, Baseline throughput earned per GiB, Burst throughput per TiB, Credit bucket size per TiB stored, Sustained throughput the workload drives, Provisioned throughput price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Is Elastic throughput better than Bursting?
Elastic removes the credit model entirely and bills per GB read and written, which suits spiky, unpredictable workloads. Bursting is cheaper for steady access that fits inside the baseline the stored data already earns.