[Bacula-users] How to troubleshoot a slow client, when there is no obvious answer

2013-01-22 Thread dweimer
If you have checked disk I/O, CPU, memory, network, on both the client and the server, all seem great, both from a statistics look, showing all running normally, with low use. Verified with read/write test on local disks, remote through he network, using regular file copies (via SMB) and

Re: [Bacula-users] How to troubleshoot a slow client, when there is no obvious answer

2013-01-22 Thread Adrian Reyer
On Tue, Jan 22, 2013 at 01:37:43PM -0600, dweimer wrote: If you have checked disk I/O, CPU, memory, network, on both the client and the server, all seem great, both from a statistics look, showing all What about many small files, possibly very many in single directories? I have seen these

Re: [Bacula-users] How to troubleshoot a slow client, when there is no obvious answer

2013-01-22 Thread dweimer
On 2013-01-22 15:34, Adrian Reyer wrote: On Tue, Jan 22, 2013 at 01:37:43PM -0600, dweimer wrote: If you have checked disk I/O, CPU, memory, network, on both the client and the server, all seem great, both from a statistics look, showing all What about many small files, possibly very many