I've noticed that when my backup server (running 1.38.2) is backing up
itself, the performance is terrible. The load average on the box goes
through the roof, and I'm getting something like 60 bytes per second.
The backup server is running on an older 1.7GHz machine, but still it
should be plenty of CPU for this simple task.
This happened after I switched to TLS. Basically, I simply configured
all clients to use TLS, including file daemon on backup server itself
(not really needed, but ended up being that way). I also had
compression turned on. Lot of job for the CPU, but it should still
yield way more than 60 bytes per second.
After I disabled TLS and compression, I got something like 1.5 MB/sec.
When I had it with compression-only, the performance was also good
(don't remember exact numbers). Any idea why TLS is slowing it down so
much? I know that same CPU needs to do encrypt and decrypt
simultaniously, but it shouldn't slow it down so much. All my other
clients (couple of them running on old sub-1GHz PIII boxes) don't seem
to suffer from this that much (the slowest ones go to around 100-200
kB/sec with TLS and compression).
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
