To perform a byte-to-byte comparison, of course, the entire file must be read (both copies). But each entire file must also be read before performing either MD5 or SHA-1 hashing. So my question becomes: Is Byte-to-byte slower not because of storage medium I/O but because of the processor-intensive comparison process, which is actually more intensive than hashing?Byte-to-byte: Most secure, but slower on huge files.
· MD5: Fastest of the hashing algorithms offered here.
· SHA-1: More secure than MD5 but slightly slower. Faster than Byte-to-byte on huge files.
Confused on verification speed
Confused on verification speed
Regarding the verification option during file copies, the help file says:
-
admin
- Site Admin
- Posts: 64849
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Confused on verification speed
Good question. MD5 uses the Windows Crypto API which seems to know a trick that I don't know. Hence it does the bigger job slightly faster than I do the smaller job. I'm embarrassed but can't help it at the moment.
FAQ | XY News RSS | XY X
XYplorer Beta Club