Copy/Paste takes longer than Cut/Paste, why? - Printable Version -Shoutbox (https://shoutbox.menthix.net) +-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58) +--- Forum: Skype & Technology (/forumdisplay.php?fid=9) +---- Forum: Tech Talk (/forumdisplay.php?fid=17) +----- Thread: Copy/Paste takes longer than Cut/Paste, why? (/showthread.php?tid=77713) Copy/Paste takes longer than Cut/Paste, why? by alegator on 09-23-2007 at 02:19 AM When transferring a file from one drive to another or within the same drive I always noticed that using Copy/Paste takes much longer than Cut/Paste, with an added hard drive activity. Is this because in Copy/Paste Windows makes an actual physical duplicate in the target location whereas in Cut/Paste it only changes the directory mapping? If so, why can't it also change the directory mapping in Copy/Paste? RE: Copy/Paste takes longer than Cut/Paste, why? by ShawnZ on 09-23-2007 at 02:25 AM
within the same drive, cut/paste will simply change the directory mapping, and copy/paste will clone the file and create a new directory mapping. RE: Copy/Paste takes longer than Cut/Paste, why? by Supersonicdarky on 09-23-2007 at 02:26 AM
Your assumption is correct. It can't just change the mapping for copying because it needs to read every single byte and then make a copy of it (+ a different dir map) RE: RE: Copy/Paste takes longer than Cut/Paste, why? by alegator on 09-23-2007 at 03:18 AM
quote:Across drives I always noticed that cut/paste is way faster than copy/paste, not as much a difference as within the same drive, but definitely faster... RE: Copy/Paste takes longer than Cut/Paste, why? by ShawnZ on 09-23-2007 at 03:45 AM
quote: programmatically, it should be faster -- but who knows how they coded it |