On Mon, 16 Feb 2009 09:02:20 +0100, Craig Ringer
wrote:
> Try setting the high priority job to -c1 (realtime) and the bacula fd to
> -c3 (idle) priority.
Bacula is already at -c3, I'm not supposed to touch the other app,
unfortunately. Thanks for your other suggestions, I'll forward those
Foo wrote:
> Thanks, that helped, although there is still some packetloss (about a
> quarter of the previous value).
Try setting the high priority job to -c1 (realtime) and the bacula fd to
-c3 (idle) priority.
If that's still not sufficient, you may need to tune your disk subsystem
for low
On Wed, 11 Feb 2009 17:13:46 +0100, Foo wrote:
> On Tue, 10 Feb 2009 18:41:53 +0100, Mike Holden
> wrote:
>
>> You could also look at using iotop and iftop to check disk and network
>> throughtput at the problem times to see what is going on.
Looked up iotop, unfortunately it requires kernel 2.
On Tue, 10 Feb 2009 18:41:53 +0100, Mike Holden
wrote:
> Foo wrote:
>> Hi,
>>
>> I'm doing a backup on a Debian Etch server which runs a network/time
>> critical app at -20 niceness, but even with nice -n19 bacula-fd still
>> causes glitches (packetloss).
>>
>> They seem to happen when the back
Foo wrote:
> Hi,
>
> I'm doing a backup on a Debian Etch server which runs a network/time
> critical app at -20 niceness, but even with nice -n19 bacula-fd still
> causes glitches (packetloss).
>
> They seem to happen when the backup starts and ends, during the backup
> (doing 20-23 MB/s) there is
Hi,
I'm doing a backup on a Debian Etch server which runs a network/time
critical app at -20 niceness, but even with nice -n19 bacula-fd still
causes glitches (packetloss).
They seem to happen when the backup starts and ends, during the backup
(doing 20-23 MB/s) there is no problem. An incr
