On Thu, 12 Oct 2023 07:36:17 -0500, Dale wrote: > Neil Bothwick wrote: > > On Wed, 11 Oct 2023 17:52:58 -0500, Dale wrote: > > > >> It only does this when I'm copying files over. Right now I'm copying > >> about 26TBs of data over ethernet and it is taking a while. Once I > >> stop it or it finishes the copy, the CPU goes to about nothing, > >> unless I'm doing something else. So it has something to do with the > >> copy process. > > Or the network. What are you using to copy? If you use rsync, you can > > make use the the --bwlimit option to reduce the speed and network > > load. > > > > > > > Reduce? I wouldn't complain if it went faster. I think it is about as > fast as it is going to get tho.
And that may be contributing to the CPU usage. Slowing down the flow may make the comouter more usable, and you're never going to copy 26TB quickly, especially over ethernet. > While I'm not sure what is keeping me from copying as fast as the drives > themselves can go, I suspect it is the encryption. If you're copying over the network, that will be the limiting factor. -- Neil Bothwick Nixon's Principal: If 2 wrongs don't make a right, try 3.
pgpv3iDV0bfu7.pgp
Description: OpenPGP digital signature
