Moving on-premises block storage to AWS? The "divide by 625 MBps" sizing approach comes out wrong
Moving on-premises block storage to AWS? The "divide by 625 MBps" sizing approach comes out wrong — measured session and queue counts What this article does and does not cover: it covers the measured failure of the "divide by 625 MBps" sizing approach, and four configuration failures hit before mounting. It does not cover performance conclusions, a comparison against file protocols, or…
A recent article has raised concerns over the widely used method of dividing the required throughput by 625 MBps to determine the number of sessions needed when migrating on-premises block storage to AWS. The author conducted tests that revealed this simple approach does not yield accurate results. Measuring the connection count between a single EC2 client and a single FSx for ONTAP file system, the article highlights the discrepancies in performance when using this method.
The findings indicate that this approach fails to capture the true potential of the system and should not be relied upon for sizing block storage configurations in AWS.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
