I've found that when gzip is running on my own, and clients systems it's
usually using 95+% of one cpu, which isn't a problem for us or them because
the machines either have a spare cpu, or aren't doing anything at the time.
more of a problem for bigger sites where your server will always be busy...
The dumper itself usually takes very little cpu time.
-------------------------------------------------------------------
>I still noticed that the dumper process is the bottleneck, but dumper now
>gets a performance of about 3 - 4 Kbps (iso sometimes down to 250bps).
Are you sure it's dumper? Or is that just the symptom? For instance,
it could be the dump program on the client, disks on the client,
SCSI termination (or lack there of), bad cables, bad controller, your
network connection, other workload on the system at the same time,
disk/controller/bus contention between the backed up disk and holding
disk, ditto for the tape drive if the image goes direct to tape, etc.
>Gerhard den Hollander
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
