ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > General Software Discussion

"Do copy acceleration utilities actually lower file transfer speeds?"

<< < (3/4) > >>

40hz:
My original question remains: is a *real* copy acceleration utility for Windows theoretically possible? How come none of the available utilities seem to achieve the acceleration it promises?
-paulobrabo (August 10, 2012, 12:59 PM)
--- End quote ---

I think within a given PC, file copying speeds would be more dependent on hardware (and possibly drivers) than anything else. Windows is a mature operating system. So I'd suspect Microsoft has by now identified and taken care of most of the safely fixable boottlenecks. Which would account for why copy accelerators had a more pronounced effect under XP - and may well be getting in the way with newer versions of Windows.

Just guessing though. :)

Network file copying is a different matter however, and there are definitely areas for improvement there. And also lots of ways to optimize and tweak network performance. However, hardware can once again play a major role since a faster network infrastructure yields faster transfers even if all other factors remain the same. So sometimes it's just more practical to put in faster NICs and data switches to get 'wire' transfer speed increases rather than bother with too much protocol or OS tinkering.


Nod5:
file copying in Explorer in Windows 7 is sometimes slowed down by having to deal with dialogs like this

It is sometimes useful but I dislike that it pops up even for files that are exact copies. A smarter file manager would do a file hash comparison and skip copying that file if the hashes match, all in the background.

f0dder:
A smarter file manager would do a file hash comparison and skip copying that file if the hashes match, all in the background.
-Nod5 (August 12, 2012, 04:44 AM)
--- End quote ---
That would be pretty disastrous speed-wise - definitely not something you want for a general file-copying routine :)

x16wda:
That's very strange... I did a comparison a couple years ago between Windows and several of the other accelerators (Fastcopy, Supercopier 2, Copy Handler, FF Copy, Ultracopier and a couple more, all that would be no cost for commercial use, which ruled out Teracopy) to see what they did locally and over a lan.  It wasn't a double blind, duplicate hardware kind of test but it was the same sets of files and targets.  In those tests Fastcopy was the clear winner speed-wise (although the interface is lousy, which is not an issue if you're scripting something).  A few others were clumped behind that, generally not too far behind.  Windows was never the fastest option, although some of the utilities were slower in some of the tests.

I don't have the details any more, but that said, the real end result is that I have Supercopier installed on my personal PCs.  It was almost as fast as Fastcopy and does a good job with the management part that has been mentioned, and it has always been reliable.  That was the surprising part to me -- with half of the other utilities I tested, I had issues with installation, lockups or copy failures.  To my mind that immediately ruled them out.

That was back when I could do stuff like that for my previous employer.  I can't recall if was running XP or 7 at the time, but would have been 32 bit in eiother case.  Would probably be worth revisiting.

Nod5:
A smarter file manager would do a file hash comparison and skip copying that file if the hashes match, all in the background.
-Nod5 (August 12, 2012, 04:44 AM)
--- End quote ---
That would be pretty disastrous speed-wise - definitely not something you want for a general file-copying routine :)
-f0dder (August 12, 2012, 11:24 AM)
--- End quote ---
I think it could be designed to avoid speed-problems in many use cases. First, the hashing would only be done for identical file names in source and target folder. Second, the user could configure how large files to do the automatic hash check for, depending on system speed and user preference. For example if the operation only ran for same named files under 100 Megabytes in size then would there really be any problematic slowdown on computer with a newish CPU? If you are copying thousands of files with name conflicts then yes, delays will add up. But a smart file manager could also calculate the total number of such conflicts prior to operation and, if the number reaches some upper limit, skip auto hashing and display the regular interaction popups (including the checkbox labelled something like "do this action for all similar files"). So smartly designed it could avoid the possible slow-down cases and still save the user time and attention in all other cases.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version