Filipe Brandenburger wrote:
>
> On Mon, Jul 6, 2009 at 23:57, Les Mikesell<lesmikes...@gmail.com> wrote:
>> The only thing that seems slightly strange in the graphs is the load average
>> going to 12 as the backups start and staying there a couple of hours.
>> Normally
>> that's the average number of 'other' processes that are waiting for CPU but
>> otherwise runnable (i.e. not themselves blocked on i/o).
>
> I used to think that, but in fact processes that are blocked in disk
> i/o (the ones in "D" state) do count in load average. So the load
> average of 12 in this case probably means processes writing to the
> disk.
That must be a Linux quirk (bug?) but it does explain some numbers I've
seen. Regardless, there shouldn't be that many things running.
>
> Stephen, it seems strange to me that there are 8 BackupPC_nightly
> processes running, have you increased $Conf{MaxBackupPCNightlyJobs}
> from 2 to 8?
>
> I would suggest you start by setting $Conf{MaxBackupPCNightlyJobs}
> back to 2 or even to 1. If you set it to 1 and it can't finish its job
> in 24h, then increase $Conf{BackupPCNightlyPeriod} to 2 or 4 so that
> only 1/2 or 1/4 of the pool is processed each night.
More importantly, BackupPC_nightly shouldn't overlap with backup jobs if
possible.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
