Mark Knecht wrote: > > > On Sat, Sep 23, 2023 at 9:22 AM Rich Freeman <ri...@gentoo.org > <mailto:ri...@gentoo.org>> wrote: > > > > On Sat, Sep 23, 2023 at 8:04 AM Dale <rdalek1...@gmail.com > <mailto:rdalek1...@gmail.com>> wrote: > > > > > > I'm expecting more of a consistent throughput instead of all the > > > idle time. The final throughput is only around 29.32MB/s according to > > > info from rsync. If it was not stopping all the time and passing data > > > through all the time, I think that would improve. Might even double. > > > > Is anything else reading data from the NAS at the same time? The > > performance is going to depend on a lot of details you haven't > > provided, but anything that reads from a hard disk is going to > > significantly drop throughput - probably to levels around what you're > > seeing. > > > > That seems like the most likely explanation, assuming you don't have > > some older CPU or a 100Mbps network port, or something else like WiFi > > in the mix. The bursty behavior is likely due to caching. > > > > -- > > Rich > > Let's not forget that Dale also likes to put layers of things on his > drives, LVM & encryption at a minimum. We also don't know anything > about his block sizes at either end of this pipe. > > I would think maybe running iotop AND btop on both ends would give some > clues on timing. Is the time when gkrellm is idle due to the host disk > not > responding or the target getting flooded with too much data? > > - Mark
This is true. I have LVM on the bottom layer with dm-crypt, cryptsetup, above that and then the file system. It's the only way I can have more than one drive and encrypt it. Well, there's ZFS but I already been down that path. ;-) I posted in another reply a picture that shows this same thing happening even when the copy process is on the same rig and even on the same LV. That should rule out network issues. I think as was pointed out, it is transferring the data until the cache fills up and then it has to wait for it to catch up then repeat. It could be encryption slows that process down a good bit, it could be LVM, or both. I do know when I did a test copy to the NAS box when the drives on the NAS box were not encrypted, it was a good bit faster, about double or more. Once I got LVM and the encryption set up, it was slow again. Also just like when using Truenas. Anyway, I think the network is ruled out at least. I'm not sure what can be done at this point. If it is a cache or drive can't keep up issue, we can't fix that. At least it does work, even if it takes a while to get there. :-D Only took almost two weeks to copy over to my backups. ROFL Thanks to all for the ideas, help, suggestions etc etc. Dale :-) :-)
