![]() for the long and boring technical explanation, suck on this (v=vs.85). There's actually a fairly complex process going on behind the scenes in what would appear like a simple copy between drives. the effect may also be more pronounced since you have 16GB ram and I believe windows tunes the cache up or down according to how much ram you have. Think of it like pouring water into a funnel, and having to slow down how fast you're pouring once its full to the top. at that first pause windows has filled the system cache at the full speed of the source disk, and pauses to allow the destination device to catch up before taking another read gulp. and it appears more pronounced like the way described when copying between devices of different speeds, and you're copying to a device that's slower than the source. the "freeze" effect is illusory and has more to do with the "lazy" way windows calculates throughput - more of a moment to moment average than instant-feedback. First, convert 2 minutes to seconds by multiplying 2 by 60, which is 120. For example, you might have transferred 25 MB in 2 minutes. Plug the amount of data (A) and transfer time (T) to solve for the rate, or speed (S), into the equation S A รท T. ![]() Totally normal, because all disk based file data I/O traverses the system cache. Calculate the transfer speed by dividing the amount of data by the transfer time.
0 Comments
Leave a Reply. |