Editing 612: Estimation

Jump to: navigation, search

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 12: Line 12:
 
The reason why this happens is because Windows calculates the estimate purely based on the current transfer rate, which if we were to continue with the car scenario put forth by Randall, is like giving an ETA based on the speed the car is currently at with no consideration of the future, such as traffic lgihts, traffic jams, or expressways. Transferring files are limited by various factors such as how fast the files can be read, how quickly the disk can be written to, and even the size of each file themselves (think the difference between carrying a large box versus having to carry a hundred miscellaneous items).
 
The reason why this happens is because Windows calculates the estimate purely based on the current transfer rate, which if we were to continue with the car scenario put forth by Randall, is like giving an ETA based on the speed the car is currently at with no consideration of the future, such as traffic lgihts, traffic jams, or expressways. Transferring files are limited by various factors such as how fast the files can be read, how quickly the disk can be written to, and even the size of each file themselves (think the difference between carrying a large box versus having to carry a hundred miscellaneous items).
  
βˆ’
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 avoids the problem by doing away with the time estimate.
+
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 title text refers to the fact that if the connection is lost, and data can no longer be transmitted, the estimation just gets larger and larger as time goes on rather than realizing that no data being sent means there is no connection. This is a behavior that occurs on {{w|Microsoft}} network connections even when the connection is not lost. Kubuntu avoids this problem, but not that of wide fluctuations, by including only the past few seconds in its estimate. If there has been zero progress within the averaging interval, it reports "Stalled".
 
The title text refers to the fact that if the connection is lost, and data can no longer be transmitted, the estimation just gets larger and larger as time goes on rather than realizing that no data being sent means there is no connection. This is a behavior that occurs on {{w|Microsoft}} network connections even when the connection is not lost. Kubuntu avoids this problem, but not that of wide fluctuations, by including only the past few seconds in its estimate. If there has been zero progress within the averaging interval, it reports "Stalled".

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)