On Mon, 21 May 2007 12:49:12 -0400 Jordan Desroches <[EMAIL PROTECTED]> wrote:
> I've done a bunch of testing since my last post, and the slowdown > appears to be CPU usage on the client file daemon (bacula-fd). bacula-fd > consumes all the cpu resource it can get, and tends to transfers data > faster (40 MB/s) on to the director on a machine with better CPU, even > though the disk array on the slower machine (28 MB/s) was faster > (similar data sets). I'm using MD5 hashes and compression is not turned > on (also not explicitly turned off, if there is such a command). Is it > normal for the file daemon to consume 100% of a cpu, or am I doing > something wrong? Any time I've seen high CPU usage on the FD, it's been the result of compression being turned on and has been solved by either lowering the aggressiveness of compression or turning it off altogether. So my first advice would be to verify whether compression is on or not. Check your job defaults. Is this a POSIX system? Run top(1) and see where the CPU time is going: user? system? io? -- Bill Moran Potential Technologies http://www.potentialtech.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
