So previously i was using rysnc between two mybook live drives where rysnc daemon would run on of the drivers.
Gigabit network all around.
Now i got two my cloud drives. While Samba read write on these drives is more than 2x as the mybook live
Rsync is almost 50% slower.
rsync between the mybook live i would get 24MB/Sec… on the my clud drives i get 14-15MB/sec.
WHY IS THIS…PLEASE CAN ANYONE HELP ME
i’ve looked everywhere. im not using any compression, syncing based on size only
as rsync is cpu bound i.e if using its algorithm to determine file differences. but im not even doing that. So why is that with a dual core CPU at 1.3 ghz is slower?
Is rsync not aware of dual core?
i notice that cpu usage is only about 30% when rsync is running
oh wow (looks like i cannot SAY ) …good you had a backup… I’ve made mistakes like this once also…
ran a command once rm-rf command like rm -f /shares/data/ IMG *
didnt notice for a few seconds that there was a space between IMG and *… freakin thing was wiping out my entire data folder which has everything… hehe.
I did a similar test a few days ago but the other way around i.e MBL to CLOUD. I still got the same speed.
However in all my cases/tests, the receiving device’s cpu hardly goes up from idle. Where as the sending goes up alot.
Note: receiving side is where the daemon runs in my scenario
now this gives me an another idea!! Is there a way to reverse the rsync in such a way that instead of sending data, the other drive pulls data?
Ok, I’ll bite… Why must they? RSYNC isn’t even an advertised component. So why is the onus on them to fix it?
And the more I look at it, yeah, it does make sense. Even though the Cloud is Dual Core (and beats the pants off the MBL in terms of file transfer performance), RSYNC being CPU-bound to a single core makes it slower since one individual ARMv7 core is slower than the PowerPC CPU in the MBL.
This definitely displays a weakness of rsync – it’s very CPU intensive because it computes checksums TWICE – once on each end. THAT is what’s chewing up the CPU.
Ok, I’ll bite… Why must they? RSYNC isn’t even an advertised component. So why is the onus on them to fix it?
And the more I look at it, yeah, it does make sense. Even though the Cloud is Dual Core (and beats the pants off the MBL in terms of file transfer performance), RSYNC being CPU-bound to a single core makes it slower since one individual ARMv7 core is slower than the PowerPC CPU in the MBL.
This definitely displays a weakness of rsync – it’s very CPU intensive because it computes checksums TWICE – once on each end. THAT is what’s chewing up the CPU.
Isn’t rsync the basis for their Safepoint utility? I know it is in my MBL. Maybe someone can verify if safepoint in the MyCloud is slower than MBL.
Isn’t rsync the basis for their Safepoint utility? I know it is in my MBL. Maybe someone can verify if safepoint in the MyCloud is slower than MBL.
Yes and no. What’s being duscussed above is a simple rsync using the rsync process at the client (with specific options) as well as rsync daemon at the receiver.
The safepoint process doesn’t use the rsync daemon at the receiver - it uses Samba as a transport. So the receiver isn’t doing much of anything during a Safepoint. The only process with higher CPU is smbd; and the Cloud was only about 30-40% CPU while the safepoint was running. Above, the CPU was 100%. It also appears that, on the sender, it’s not a single-threaded process as it is above. It uses multiple instances of rsync at the sender:
Quesiton on these safepoints. I’ve never used them.
Is a safe point like a system image as in like a one big zipped up file type of thing or is the data structure the same as the source drive. By that i mean, can you simply access the files like you do on a regular mapped drive?
If thats the case, i could simply use the safe point feature. But i have a feeling that that process doesnt just update changed data, rather it copies everything all over?
Quesiton on these safepoints. I’ve never used them.
Is a safe point like a system image as in like a one big zipped up file type of thing or is the data structure the same as the source drive. By that i mean, can you simply access the files like you do on a regular mapped drive?
It’s the same structure, but in a different place. It stores them in in a share you choose.
Yes, you can access the files via a mapped drive.
I don’t think it’s doing block-level change-data via Safepoint, but it is NOT resending files that are already present.