@Iddrisu, Alhassan Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
- For better understanding the issue: May I know, how are you measuring the speed performance(You are using Azure speed test tool to check the speed: https://www.azurespeed.com/Azure/Download )?
- Are you using the Azure Files Storage in your scenario?
- How are you trying to upload(Portal, CLI, Powershell, REST API, Code? Also from on-prem- or AzureVM)?
There is no throttling on the Azure side, refer to below article. If the network and client machine can handle the traffic then we will send it.
If you are using Azure files: You might see slow performance when you try to transfer files to the Azure Files service. If you don't have a specific minimum I/O size requirement, we recommend that you use 1 MiB as the I/O size for optimal performance.
If you know the final size of a file that you're extending with writes, and your software doesn't have compatibility problems when the unwritten tail on the file contains zeros, then set the file size in advance instead of making every write an extending write.
Use the right copy method:
- Use AzCopy for any transfer between two file shares.
- Use Robocopy between file shares on an on-premises computer.
Here's a guide for troubleshooting high E2E latency: https://learn.microsoft.com/en-us/azure/storage/common/storage-monitoring-diagnosing-troubleshooting#metrics-show-high-AverageE2ELatency-and-low-AverageServerLatency
Additional information: Sometimes your proxies/VMs or whatever runs in the same datacenter, network requests does not leave the local network and the speed then depends on the infrastructure. (routers, firewalls, cables, etc). I'm sure they won't limit speed between their own infrastructure so services hosted on the same network works at full speed.
Note: Windows OS/Windows Explorer is configured by default, it uses a 4K block size that will produce slower speeds for SMB compared to AzCopy/Storage Explorer which uses REST API.
Additional information: Sometimes your proxies/VMs or whatever runs in the same datacenter, network requests does not leave the local network and the speed then depends on the infrastructure. (routers, firewalls, cables, etc). I'm sure they won't limit speed between their own infrastructure so services hosted on the same network works at full speed.
Note: Windows OS/Windows Explorer is configured by default, it uses a 4K block size that will produce slower speeds for SMB compared to AzCopy/Storage Explorer which uses REST API.
Azure Files scalability and performance targets
Please let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.