I'm doing the initial Backblaze upload to B2 and I'n noted that I'm getting around a solid 10Mbps. I'm operating in the evening and weekend hours, and this would be great but for the fact I have a solid 100 Mbps fiber connection.
The backup is from a Synology, using cloudsync.
So the question is how do I saturate said connection, because a quicker upload of data would be advantageous especially if it does not to interfere with day-to-day usage.
So far I've looked at traffic shaping giving it higher priority and ignore any global bandwidth limits but alas it seems to still only give me 10Mbps.
What am I obviously missing here?
@Richard_W There are multiple things that would limit you upload speed.
1. The Synology box itself, I assume it has a gigabit ethernet port?
2. Traffic shaping on your router
3. Backblaze might be restricting your upload speeds at their end. They only have so much bandwidth in their incoming pipe so likely restrict things at there end to allow as many users as possible to upload at once.
If I was in their shoes I would rather have two customers uploading at 10Mbps at the same time than have one uploading at 100Mbps and 9 other potentially queued.
Yeah the Synology we have a bonded connection to an aggregation group on the switch. So I'm pretty sure no bottleneck there.
Traffic shaping is set to give Backblaze unfettered access.
I'm guessing it's door number three; Backblaze restricting?
What do you get when you use their speed test?
Because the graph is flat lined that indicates to me that something is limiting the performance.
It could be BackBlaze itself. It could be a setting in the client app on your end. If you have any traffic shapping configured on the MX then it could also be that.
But the issue is something is imposing a performance limit - rather than you need to optize the network to make it faster.
Apparently that form of traffic shaping (above) had no affect on increasing upload speed over Global bandwidth limits > Per-client limit.
The traffic was being held to per-client limit. I came to this elementary conclusion with the simple removal of per-client limit one evening, as is my wont.
So I guess I'll need to re-look at this unless anyone else has encountered this?