Sean Clark <smclark AT tamu DOT edu> writes:

> In my experience, slow performance like this (i.e. <5MB/s on at least
> 100Mb ethernet) usually turns out to be the client's fault.
> Compression seems to be a very common culprit.  Try switching
> compression off completely and see how much of a difference that
> makes.  The latency introduced by waiting for compression - even
> pretty fast compression - seems to substantially choke throughput
> down.

the compression in bacula-fd is also running in a single thread, so you
only exploit one cpu core.  if your disks can handle it, consider
splitting up the client job and run the jobs concurrently.  or just turn
off compression -- usually the data is kept in compressed form on the
client anyway.

-- 
Kjetil T. Homme
Redpill Linpro AS - Changing the game


------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users