Skip to main content
Azure Speed Test

Large file upload speed test

Evaluate Azure Blob Storage upload performance by pushing your own large file to different regions and tracking throughput in real time.

Large file upload test

Test Steps
Select regionChoose file & settingsView results
Test file
Block size

4 MB+ typically works best for large files.

Concurrency

Higher values increase parallel uploads but may be limited by bandwidth.

Select a target region and file before starting the upload test.

Frequently asked questions

When should I use this tool?

This tool is useful when you need to:

  • Diagnose slow Azure Data Factory copy activity performance
  • Test upload bandwidth from on-premises to Azure before migration
  • Verify network throughput for Self-hosted Integration Runtime
  • Compare upload speeds across different Azure regions
  • Benchmark your network connection for large data transfers
How does Large File Upload Speed Test tool work?

The performance test tool:

  • Uploads your test file to temporary Azure Blob storage in your selected region
  • Measures actual transfer speeds accounting for network conditions
  • Calculates and displays detailed performance metrics
  • Automatically removes the test file after completion

Results can vary based on network conditions, file size, and selected parameters.

How should I choose block size and concurrency?

Block Size: Larger blocks (4 MB+) typically work better for files over 100 MB but require more memory.

Concurrency: Higher values can improve speed but may be limited by bandwidth and local resources.

Start with default values and adjust based on your results.

Why do test results vary between runs?

Performance variations are normal and can be attributed to multiple factors:

  • Network path changes and internet traffic conditions
  • Regional network congestion
  • Local network quality and bandwidth availability
  • Distance to the selected Azure region
  • System resource availability

For the most accurate assessment, we recommend running multiple tests at different times and comparing the results.