>... the copy command consumes a LOT of system resources (mainly
>disk of course) and my server almost look dead from time to time. I've tried
>nice -n 15 to make the cp command a bit more nice, but it doesn't seem to
>work...
The "nice" command only affects CPU priority, which obviously won't help
your problem.
>Any suggestions? This is a RedHat Linux 6.2 system.
Buy more hardware :-).
I don't know much about Linux, but here are some very general ideas:
* Put the main disks and the temp disks on different controllers.
* Upgrade the disks to faster versions.
* Upgrade the controller(s) to faster versions.
* Get a system with a faster main bus or multiple bus's.
You should also examine the various system options (BIOS, etc) and/or
talk with other Linux folks about whether there are any tunables in there,
or if there are "good" and "bad" hardware combinations.
You should also make sure there isn't anything silly going on, such as
bad termination, bad cables, total cable length too long, non-FW device
before FW device in the chain, etc.
I doubt software will be able to fix this. You might do the copy yourself
(as I recall, you were converting to Perl?) and add some (u)sleep time
every few hundred I/O operations. Make the amount of time and number
of operations tunables because you will for certain need to play with
them a lot to get it balanced right.
>/Fredrik Persson
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
