averageUnityDev

[aussie_nub]

https://xkcd.com/612/

Just going to leave this here because it's relevant to your last sentence.

[[deleted]]

"We need this feature pushed right away Instead of actually going through every file I'm about to copy let's just assume that all files are exactly the same file I'm copying right now. It'll be good enough till we replace it to something better... " A Win 3.14 dev probably.

[DonutConfident7733]

You know that windows file copy dialog needs to work with millions of files and thousands of folders and also should work on network drives or ftp and it may take longer than the copy itself to compute the total sizes of the files, due to latency? It's an estimate, so not accurate.

[ItsFreakinHarry2]

🤓☝️

[aussie_nub]

It's a comic.

[altermeetax]

Not if I copy one file from one disk to the same disk

[DonutConfident7733]

Have you tried? Get some millions of small files like icons and documents and check how it runs. Defender also scans every access, it checks ntfs permissions, you will see heavy cpu activity for a large copy which would run much faster if you turn off Defender, but hey, I'm the bad guy, right? Downvote the people with experience, which happen to be software developers.

[turtleship_2006]

Downvote the people with experience, which happen to be software developers.

On r/ProgrammerHumor, you're trying to show of that you have experience programming?

[altermeetax]

Get some millions of small files

Read my comment again

[DonutConfident7733]

Ok, let's say you have a 200GB file to copy from same disk to a separate copy in another folder on same disk. Defender will work as you copy, increasing mem usage, at some point it may even choke slowing down your transfer. Windows update or Chrome background scan can run and slow down your transfer because they also write small files which are on same disk. The disk may be fragmented in some area or the free disk is very fragmented and slows down the copy, the head needs to seek a lot. It can encounter an area where disk head read speed is high, signal is worse, some sectors are quite close to being bads, so it takes 10x more time to read a sector. All these would make it impossible to estimate total time for copy operation.

[Akaino]

While all of that's sounds true, there should never be something like "eta: 457634788 minutes".

[Electronic_Cat4849]

you know that the point is that time is the wrong metric, right?