Kā Windows nosaka, cik ilgs laiks ir nepieciešams, lai veiktu darbību ar failu?

Satura rādītājs:

Kā Windows nosaka, cik ilgs laiks ir nepieciešams, lai veiktu darbību ar failu?
Kā Windows nosaka, cik ilgs laiks ir nepieciešams, lai veiktu darbību ar failu?

Video: Kā Windows nosaka, cik ilgs laiks ir nepieciešams, lai veiktu darbību ar failu?

Video: Kā Windows nosaka, cik ilgs laiks ir nepieciešams, lai veiktu darbību ar failu?
Video: Add Open in Terminal Command to Nautilus Context Menu in Ubuntu Linux - YouTube 2024, Aprīlis
Anonim
Windows atlikušie aprēķini ir pietiekami, lai laiku pa laikam vadītu ikvienu traku, bet vai jūs kādreiz esat domājuši par to, kā sistēma Windows nosaka šos laikus? Šodienas SuperUser Q & A ziņai ir dažas atbildes par ziņkārīgs, tomēr neapmierināts, lasītāja jautājumu.
Windows atlikušie aprēķini ir pietiekami, lai laiku pa laikam vadītu ikvienu traku, bet vai jūs kādreiz esat domājuši par to, kā sistēma Windows nosaka šos laikus? Šodienas SuperUser Q & A ziņai ir dažas atbildes par ziņkārīgs, tomēr neapmierināts, lasītāja jautājumu.

Šodienas jautājumu un atbilžu sesija mums priecājas par SuperUser - Stack Exchange dalību, kas ir kopienas vadīta Q & A tīmekļa vietņu grupa.

Windows 8.1 failu pārsūtīšanas logu ekrānuzņēmums pieklājīgi no im tiešām famecore.

Jautājums

SuperUser lasītājs 'im really famecore' vēlas uzzināt, kā Windows nosaka laiku, kas nepieciešams, lai veiktu operāciju ar failu:

I wanted to know if there is an equation that Windows uses to determine how long it takes to perform an action with a file such as: deleting, copying, erasing, or installing.

Image
Image

For example, when I delete a file and Windows says Time remaining: 18 seconds, how is it calculating this number, and what does it use to calculate it?

Vai Windows izmanto īpašu vienādojumu, lai noteiktu atlikušo laiku, lai veiktu operāciju, vai arī tas vienkārši nodrošina "vislabāko minējumu" aplēsi?

Atbilde

SuperUser atbalstītāji Valmiky Arquissandas un Richard ir atbilde mums. Pirmkārt, Valmiky Arquissandas:

Have you noticed that it usually does not give you any estimates during the first few seconds?

That is because during the first few seconds, it just does the operation it has to do. Then, after a short amount of time, it knows how much it has already copied/deleted/etc, and how long it took. That gives you the average speed of the operation.

Then, divide the remaining bytes by the speed, and you have the time it will take to complete the operation.

This is elementary school math. If you want to travel 360 km, and at the end of the first minute you have traveled 1 km, how long will it take you to reach your destination?

Well, the speed is 1 km/minute, so that is 60 km/hour. 360 km divided by 60 km/hour gives you an estimated time of 6 hours (or 360 km / 1 km/minute = 360 minutes = 6 hours). Since you have already traveled for one minute, then the estimated time left is 5 hours and 59 minutes.

Substitute travel with copy, km with bytes, and that answers your question.

Different systems have different ways of estimating time. You can take the last minute and the estimates may vary wildly. Or you can take the full time, and if the speed actually changes permanently, your estimates may be far removed from reality. What I described is the simplest method.

Seko Richardsa atbilde:

If you are interested, this question tells you how Windows and OSX formats the time left into the progress bar once it has an idea how long it has remaining.

When shortening time expressions in progress dialogs, should they be rounded up or down?

Raymond Chen, a developer on the Windows team at Microsoft, confirms this algorithm (see Valmiky’s answer above) in a posting on his blog. He also explains why it can be wrong.

Why does the copy dialog give such horrible estimates?

Vai kaut ko pievienot paskaidrojumam? Skatieties komentāros. Vēlaties lasīt citas atbildes no citiem tehnoloģiju savvy Stack Exchange lietotājiem? Šeit skatiet pilnu diskusiju pavedienu.

Ieteicams: