[BUG?] PBS Sync (pull) completely ignores bandwidth setting

[yummiweb]

Backup Server 4.1.4 (other versions not tested)

The sync between my PBS (offsite backups) runs at a fixed 8 Mbps.
Regardless of the setting in /etc/proxmox-backup/sync.cfg (configured via GUI).

An external limit is ruled out because even a lower value (e.g., 1 Mbps) is ignored.
Even with a 1 Mbps setting, the transfer runs at approximately 8 Mbps.
Even a blank value is ignored.

Tested by running the job on demand (click) in the GUI, via a scheduled command (GUI), and by running the job in the console – none of these make a difference.

I created a completely new sync job for testing purposes, and this one also ignores all bandwidth settings.

Can anyone reproduce this behavior? Before I report it as a bug somewhere (where?)?

Greetings Yummiweb

 

[UdoB]

Even with a 1 Mbps setting, the transfer runs at approximately 8 Mbps.

The setting in "Add: Sync Job Pull - Pull Direction" accepts a "Rate Limit:" in MiB/s = Mebi Bytes.

The usual (but not all) bandwidth diagrams show Bits per second.

Any chance this was the culprit...?

 

[yummiweb]

The setting in "Add: Sync Job Pull - Pull Direction" accepts a "Rate Limit:" in MiB/s = Mebi Bytes.

Thanks for the heads-up! I've noticed that myself in the meantime.

It might be interesting to understand why I didn't see any speed difference in my tests:

This was probably due to sshuttle, which in this configuration (standard buffer or no buffer specified) somehow limited the speed to 8 Mbps. So the upper limit was around 8 Mbps despite the job being set to 16 MiB/s, and the 1 MiB/s setting also happened to correspond to the 8 Mbps I measured.

With the sshuttle option "--latency-buffer-size=131072", I'm now getting more realistic values.

Thanks for your input!