> Hi, I probably can't help. The only time I had rsyncHi, thanks anyway for trying.> suggest is that your network bandwidth is being used up > by something else (whatever is using up that 4MB/s) butChances are low because this value appears exactly when I launch the rsyncing.> be another 8MB/s to spare. Wireshark could help you > identify what the traffic is.Not sure that setting up Wireshark is valuable since I almost finished the transfer but thanks!>> problem is the disk I/O speed on the gobook itself. IsI use it daily and it works very well(it was a very high-end laptop for the beginning of the 21st century, costing something like $2500. The biggest problem is the lack of RAM)> that possible? I have no idea how old it is or what old > I/O speeds were like. Can you run top on the gobook? IsI've of course done it. I'm forced to do it hundreds of time each day anyway.> there iowait? If so, that might be the problem. Also,Where can I see this information?> if the gobook is really old, its network interface > might only be 10Mbps, but even that should mean 1.25MB/s > (if the disk I/O speed can keep up).I've of course verified this, it's 100mb/s, and netstat indicates 11.8MB/s>> Or you could try scp just to see if the transfer speed > is any different. >I'm not very enthusiastic about setting up a SSH server on any of both laptops. One of the maddest thing is that I manage a Web storage space on an distant server(in my collaborative-ISP datacenter) and transfers are quicker in scp to this one than in rsync between computers next to each others! -- Sincerely, Stephane Ascoet
Stephane Ascoet via rsync wrote:> > Is there iowait? If so, that might be the problem. Also, > > Where can I see this information?in the header section of top: top - 12:25:13 up 43 days, 22:31, 4 users, load average: 0.18, 0.18, 0.12 Tasks: 366 total, 1 running, 365 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.2 us, 1.1 sy, 1.6 ni, 91.6 id, 2.5 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 7905444 total, 623888 free, 584760 used, 6696796 buff/cache KiB Swap: 19543036 total, 18603192 free, 939844 used. 6345040 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND On the "%Cpu" line, where it says "wa", that's the percentage of CPU time spent waiting for an I/O device. When it's high, things are bad, and there will be processes below that show "D" in the "S" column. Those processes are the ones waiting on the I/O. cheers, raf