I've had v11/postgresql13 running well for a long time but just recently it has started to run very slow. The Dir/Fd is on a Raspberry PiB with 8GB memory, Sd on a NAS mounted via CIFS over a Gbe network. I was getting a rate of ~30MB/s on the backup but this has dropped to ~1-2MB/s. I can see similar values on the network throughput page of Webmin. Backups that used to take 10h are now stretching out 10x and running into next scheduled backups. Jobs do eventually complete OK but are much too slow.
It remains the same after a couple of reboots of both the Pi and NAS. I've tried my usual suite of tools e.g. htop, iotop, glances, iostat, iperf3 but none of these are raising any flags. Iowait is < 2%, cpu < 10%, swap is 0 used, free mem is > 80%. Iperf3 network speed testing Dir<=>Fd is close to 1Gb/s, rsync transfers Pi>NAS @ 22MB/s, so I don't suspect a network issue. On the NAS, I have more limited tools but ifstat shows a similarly low incoming network rate. No apparent issues on cpu load, swap, memory, disk either. fsck ran with no errors. I thought maybe there was a database problem so I've also had a try at adjusting PostgreSQL conf per the suggestions from Pgtune but to no effect. Postgresqltuner doesn't reveal any problems with the database performance. Postgres restarted of course. Backup to S3 cloud is also slow by about 3x. It runs 25MB/s (22Mb/s previously) into local disk cache and then 2MB/s to cloud storage v. 6MB/s previously. My fibre upload limits at 50Mbs. I would have expected that a database issue would impact the caching equally but that doesn't seem to be the case. So the conclusions so far are that it's not network and not database 🤔. I'm running out of ideas now and am hoping you might have some. -Chris Wilkinson
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
