Compression is often a CPU bottleneck, did you check for cpu usage? You
can try to use pigz instead of gzip if you have available core.
How many dump are you doing in parallel? You can try to increase
inparallel, netusage and/or maxdumps.
You can use amplot and amstatus to check amanda perfor
Amit,
I don't think you told us how many client systems, compression
can be done on the client or the server. Also, besides the inparallel
and maxdump settings, are you short on work area - as Jean-Louis
said, the amplot output will help you spot those bottlenecks.
Brian
On Thu, Mar 14, 2013 at
Thanks gurus, let me share more info about my setup:
Network-speed:
On main server:
# dmesg | grep -i duplex
bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
On few clients:
# dmesg | grep -i duplex
tg3: eth0: Link is up at 1000 Mbps, full duplex.
# dmesg | grep -i duplex
[ 13.122791] e1
I am sharing her more Info:
cpu usage
On server (Intel® Xeon® series Quad core processors @ 2.66GHz)
# ps -eo pcpu,pid,user,args | sort -r -k1 | head
%CPU PID USER COMMAND
6.0 26873 33 /usr/bin/gzip --fast
4.3 26906 33 /usr/bin/gzip --fast
27.7 30002 ntop ntop
2.1 26517 3
