8 hours to synchronize 57 GB

[inventor1949]

Hi what is normal sync time for 57 GB it seams to me 8h is to long

2-06-13-18-15.jpg (116.5 KiB) Viewed 1529 times

1-06-13-18-09.jpg (116.42 KiB) Viewed 1529 times

[Plerry]

Perhaps your "problem" is as described here.
Besides that: you have close to 100.000 files for a total of ~125GB. This means an average file size of only about 1250 byte. So, you loose more time in handshaking than in the actual transfer of the file, particularly if that is to a network or even remote location.

[inventor1949]

Hi Plerry thanks
I am not on a network its from laptop to external "fail safe copying" is recommended in settings do I disabled it?

[Plerry]

It is recommended to leave "fail safe copying" enabled.
Although it may require more time, it is safer in case anything goes wrong.

But note that only the first sync will take that long, as all ~100.000 files need to be copied. Any consequetive sync will only copy files that are new or modified since the last sync.
And likely that will only involve a very small fraction of those ~100.000 files, and require a proportionally smaller amount of time.

[JDB]

Did it actually take that long after it completed? I have found that the time "Remaining" numbers are always wrong, but resolve to more reasonable numbers at the end. I've seen it jump around, reporting numbers in the range of hours, days, or minutes while watching it for just 5 minutes. But that could just be the result of my system which has file sizes ranging from 0 bytes to 20 GB. This type of mix confuses the "Remaining" calculation. I agree with Plerry that an abundance small files kills your performance. Think of it like fishing for a full meal but all you have is a small hook, and every catch is a 1 inch fish. How long will it take to fill your frying pan? (versus a big Tuna) Computers open files using a small hook known as a "handle" that has to be handled with care.

[JDB]

Also, I agree that 8 hours is too long for 57 GB. Are you backing up to USB-2 sticks or some other slow media? Are you adjusting any priorities or CPU affinity in Task Manager? What else is accessing the target "H:" at the same time? Is the target drive one of those IBM/Lenovo Uni-bays (or whatever they call it) that lets you replace the DVD with a SATA hard drive? Those things are slow as molasses.

[xCSxXenon]

Transferring the cache locations for browsers is horribly slow. Tons of tiny files, even SSDs can suffer from the overhead caused by that. I would exclude a number of folders

[inventor1949]

JDB
Did it actually take that long after it completed? No this was the first sync
Are you backing up to USB-2 sticks? Yes
Are you adjusting any priorities or CPU affinity in Task Manager? No
What else is accessing the target "H:" at the same time? No

[inventor1949]

Transferring the cache locations for browsers is horribly slow. Tons of tiny files, even SSDs can suffer from the overhead caused by that. I would exclude a number of folders

I knotest that too is there a way to exclude cache?

[inventor1949]

Also, I agree that 8 hours is too long for 57 GB. Are you backing up to USB-2 sticks or some other slow media? Are you adjusting any priorities or CPU affinity in Task Manager? What else is accessing the target "H:" at the same time? Is the target drive one of those IBM/Lenovo Uni-bays (or whatever they call it) that lets you replace the DVD with a SATA hard drive? Those things are slow as molasses.

JDB
Did it actually take that long after it completed? No this was the first sync
Are you backing up to USB-2 sticks? Yes
Are you adjusting any priorities or CPU affinity in Task Manager? No
What else is accessing the target "H:" at the same time? No

[xCSxXenon]

Yes. Run a compare and in the bottom left you can see the size and number of files in the tree structure. You can easily find the cache folders there and the right-click -> exclude