Advertisement
therube

Dup File Finder vs Dup Cleaner 206

Jun 6th, 2011
751
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.43 KB | None | 0 0
  1. dupfinder_35 aka duplicate file finder (Brooks Younce)
  2.  
  3. very basic interface, drag & drop folders to search.
  4. can edit the file types, mask (generally)
  5. can do a "Fast" Search (less accurate) that reads 1st & last 10 MB of file.
  6. - seems to be VERY quick ... /sometimes/
  7.  
  8. interface is not much, & that's the problem.
  9.  
  10. searching R:\music\*, in fast mode, took 24:31:38 used about 20 MB RAM, cpu
  11. a bit variable, but minimal < 10%. there was r/w IO throughout, whatever
  12. that means.
  13.  
  14. so now i've got the list ... & ... & 3413 duplicate files (thinking most
  15. will be jpg's, that i should have filtered out, only including mp3's, but
  16. oh well) searched 78892 files in 378 GB of space, with 10 GB wasted (what-
  17. ever that means, maybe dups?)
  18.  
  19. now with cleaner 206 ... same content, byte-by-byte, music tags excluded.
  20. 50 MB RAM ... 78974 files, 379 GB (so those numbers agree) ...
  21. 3103 duplicate groups, 6558 duplicates (20.2 GB) & it took ... 11:58.21
  22. (oh look, 206 ALSO records the time taken in its summary & that agrees TOO!)
  23.  
  24. towards the end, CPU may have varied ~15% & MEM ~70MB, but nothing so terrible.
  25.  
  26. so... 206 took MUCH LESS TIME & has MUCH better interface !!
  27.  
  28. now with 206 & MD5 ... same exact numbers except time was 9:28.96 vs. 11:58,
  29. so ~2.5 minutes quicker yet. CPU about the same, MEM ~80MB, so more yet, but
  30. nothing too spectacular.
  31.  
  32. & now with 206 & SHA1 ... EXACTLY THE SAME, time 9:23 (so same +- 6 seconds!)
  33. 98 MB RAM, so that was higher. didn't catch the CPU %?
  34.  
  35. finally 206 & SHA512 ... CPU is higher, hitting close to 25%. mem so far is
  36. only ~60 MB, ending up at 76 MB. other numbers exactly the same, time 17:06,
  37. so far more costly timewise compared to MD5/SHA1.
  38.  
  39. & dupfinder again ... (just in case "caching" makes a difference) ... perhaps
  40. the same, 24 minutes, but i lost track (of time) so i'll try yet again, this
  41. time without "Fast" ... 35:27.32, so worse yet.
  42.  
  43. FOR MUSIC, DFF35 IS A *FAIL*
  44.  
  45. ---
  46.  
  47. different for S2 etc. aka larger video/clips
  48.  
  49. DFF dups 121, searched 11339, space 253 GB, wasted 1.48 GB, 41.71 sec, not Fast mode.
  50.  
  51. DFF w/FAST same exact results, but only 8.8 seconds, so HUGE diff vs not Fast.
  52.  
  53. 206, dup groups 119, scanned 11348 (253 GB), 248 dups (2.96 GB), 40 sec b-2-b
  54.  
  55. 206 w/SHA1 same exact results, 47 sec, so, *slower* then b2b & cpu was 25%
  56. (also app "seemed" to disappear from taskbar till scan completed)
  57.  
  58. 206 w/MD5 (ditto the "disappear"), again 47 sec, though CPU only ~10%
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement