To test upload speed to a BYOS (Bring Your Own Storage) bucket:

  1. Create a large test file (if needed).
  2. Upload the file to the bucket using a web browser or s3cmd utility.
  3. Repeat several times to get an accurate result.
  4. Repeat at several different times of the day or week to see if cloud service capacity is adequate during your busy hours.

Create a Large Test File

If you do not have any files of adequate size for upload testing, you can easily create one.  We recommend a size of at least 100MB, or larger if you have a fast Internet connection.  Ideally, the upload would take at least a minute to get an accurate and consistent measurement.


To create a test file in Windows, open a PowerShell window and use the following command (in bold):

PS C:\Users\morro> fsutil file createnew testfile 100000000
File C:\Users\morro\testfile is created

This will create a file named "testfile" with a size of approximately 100MB.  Adjust the number at the end of the command line to change the file size (number is in bytes).


To create a test file in Linux or Mac, open a terminal window and use the following command (in bold):

root@server:~$ dd if=/dev/zero of=testfile bs=1M count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.0621428 s, 1.7 GB/s

This will create a file named "testfile" with a size of 100MB.  Adjust the number following "count=" to change the file size (number is in MB).

Upload the File to the Bucket

To upload the test file to your BYOS bucket, use your web browser or the s3cmd utility.  See the following documentation for AWS and Wasabi buckets.

How can I test AWS S3 file upload speed?

How can I test Wasabi file upload speed?

Repeat Several Times

Repeat the test several times to get the most accurate results.  Using several runs and large test file sizes, upload speed inconsistencies can be evened out to give you a true representation of long run upload speeds.

Repeat at Different Times of the Day or Week

To ensure that your cloud storage provider has adequate performance throughout the day or week, run several tests during your peak usage hours.

  • If your business hours are 9 AM to 6 PM PST, run the tests at 10 AM, 2 PM, and 4 PM.
  • If you have offices in other timezones, then you may wish to run tests during their peak hours also.
  • Archive and replicate sync jobs may be scheduled for off hours, so testing during those times can also be useful.
  • Test on different days of the week.  Cloud storage services may have less load on Fridays and weekends, for example.