Hi Josh,
Many thanks for your advice, good points all - I'll continue to play.
Best wishes,
Mark
On Tue, 28 Apr 2020, Josh Fisher wrote:
...
Yes. I believe the client is multi-threaded in that multiple commands can be
issued and they will each be handled in a separately spawned thread. However,
each thread will itself be sequential, so a single thread will not work on
multiple files at the same time. If you run two backup jobs in parallel, then
bacula-fd may work on two files at the same time, depending on CPU core
availability, etc.
Whether or not this helps depends on whether or not single-core CPU
performance is indeed the bottleneck. Is the single job approach CPU bound
due to compression? Or is it i/o bound anyway? For example, if on a 1G
network, then it can transfer at most 125 MB/s to the SD. If many files on
the same disk are being worked on, then it can slow down average disk access
times and perhaps the disk subsystem on the client will be the bottleneck.
A good test would be to run the single job with compression disabled. If the
throughput is much greater without compression, then perhaps splitting into
multiple jobs will help by utilizing more cores for the compression. If the
throughput isn't much different, then splitting into multiple jobs likely
won't help. Likewise for encryption.
...
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
