-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Control ANF availability zone vs VM scale set #1851
Comments
P.S. We've also seen a dependence on latency on whether the ANF networking feature is set to Basic or Standard, with Standard resulting in a 60% higher latency if everything else is the same, including availability zone (same test setup as above). This should be validated by others to see whether this number is roughly reproducible. Test resultsThese actually show again a ~100% increase in latency (from 943 IOPS to 1925), it seems like this is not highly reproducible
|
In what area(s)?
Describe the feature
Depending on whether the ANF volume is allocated in the same availability zone or in a different one, one can see very significant changes in latency
(e.g. for a 4TB ANF Premium with Basic networking, we've seen a drop from 1650 IOPS for 4KB random read to ~800 IOPS when the ANF was in a different availability zone from the D4ads v5 VM in West Europe).
It would be great if one could enforce the ANF and the scale sets to be placed in the same availability zone.
Test res
The text was updated successfully, but these errors were encountered: