Editing 612: Estimation
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 10: | Line 10: | ||
When moving or copying files using the {{w|File Explorer|Windows Explorer}}, a dialog box opens to inform the user of how many of the files being moved have been moved with an estimate of how long the rest of the files should take. However, this estimate is often subject to seemingly random and extreme changes from a time measured in seconds or minutes to one measured in hours or days. This is because Windows bases its estimate on the latest file transfer rate, which exaggerates short-term fluctuations. For instance, transfers of many small files are generally slower than transfers of a few large files, because of per-file overhead (time spent writing data describing the file's title, location, etc. to the disk). A brief slowdown may cause the system to display that the transfer will take a long time (based on the total amount of data yet be transferred and the current low speed), while a sudden burst of data moved quickly between memory caches will give a time that is much too small. | When moving or copying files using the {{w|File Explorer|Windows Explorer}}, a dialog box opens to inform the user of how many of the files being moved have been moved with an estimate of how long the rest of the files should take. However, this estimate is often subject to seemingly random and extreme changes from a time measured in seconds or minutes to one measured in hours or days. This is because Windows bases its estimate on the latest file transfer rate, which exaggerates short-term fluctuations. For instance, transfers of many small files are generally slower than transfers of a few large files, because of per-file overhead (time spent writing data describing the file's title, location, etc. to the disk). A brief slowdown may cause the system to display that the transfer will take a long time (based on the total amount of data yet be transferred and the current low speed), while a sudden burst of data moved quickly between memory caches will give a time that is much too small. | ||
| β | A better implementation would keep track of the average file transfer rate over the entire operation, which would even out the bumps and give a more accurate estimate. Windows 8 | + | A better implementation would keep track of the average file transfer rate over the entire operation, which would even out the bumps and give a more accurate estimate. Windows 8 solves the problem by doing away with the time estimate. |
The joke in the comic is the idea that this feature was actually purposely implemented and that the person who did so actually talks like that. He tells some friends on the phone how long it will take for him to arrive at their meeting point. However, like with Windows's estimation feature, he quickly changes his estimate multiple times from the extremes of days to seconds due to small fluctuations in traffic flow (like when he has to stop on a red light and then he speeds up on green). | The joke in the comic is the idea that this feature was actually purposely implemented and that the person who did so actually talks like that. He tells some friends on the phone how long it will take for him to arrive at their meeting point. However, like with Windows's estimation feature, he quickly changes his estimate multiple times from the extremes of days to seconds due to small fluctuations in traffic flow (like when he has to stop on a red light and then he speeds up on green). | ||
