On 9/28/18 10:09 PM, Gary R. Schmidt wrote: > Most of the time the various Bacula programs are waiting for I/O > operations to complete, the only time the CPU gets heavily involved is > if you are running compression. > > Just use the defaults. You won't save enough CPU, memory, or time to > justify your efforts, and if you optimise at a level that triggers some > pathological behaviour in Bacula you may not find out that critical > parts of your back-ups are garbled until it is too late.
I agree 100%. Bacula is in general I/O bound except when performing a large database operation, and *then*, most of the time, the database operation it is waiting on is I/O bound. If you can get 10% faster storage you'll probably see ten times the real-world performance gain you'd see from 20% Bacula run-time optimization. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
