However, if you have “odd data” like you have 50 million files, each is 1 byte, Backblaze could be slow on that dataset.Īfter you max the threads, click “Pause Backup” ONCE and wait at least 30 seconds for everything to pause and settle, then “Backup Now” ONCE and wait for it to crank back up. Once you get through your small files Backblaze can really rip. Check again after 6 days.īackblaze backs up in file size order small files first. Under no circumstances should you pause more than once a day.

Second, turn off all power savings modes so even your monitor stays lit all night and let it run, ESPECIALLY all night. So the client will be COMPLETELY DIFFERENT than that pure network speed test.įirst, max your # threads to 30. The actual Backblaze client must not only use the network, but your disk, plus encrypt the files, plus the destination server must replicate it across 20 servers for reliability.

If you are in New Zealand it will be slower.

For example, if you are physically in Northern California it will probably be fast. It is useful to see how your network connection to Backblaze is without involving the software. This is a generic “off the shelf” piece of software we run on a server in our datacenter.

Backblaze b2 speed test