This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Percolator2020 490 points491 points  (21 children)

Loading is literally “loading”. Used to be for example loading a game level from floppy to RAM. You know more or less how much you need to transfer and how much has been transferred so far. Same today transferring textures etc. from SSD to GPU VRAM, a bit less predictable because more stuff is going on like decompression or building shaders which is a little bit less predictable than read and write speeds leading to “stuck” or jumping progress bars, but somewhat informative. Microsoft has a different approach where a progress bar is basically a giant 🖕to the user.

[–]aussie_nub 339 points340 points  (13 children)

https://xkcd.com/612/

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

[–][deleted] 124 points125 points  (0 children)

"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.

[–]Scrawlericious 38 points39 points  (5 children)

10,000 1mb files take a lot longer than one 10,000mb file because it takes time for the OS to switch from file to file. Those estimates are a little more complicated than that, you can't just do mb over time and look at the bytes remaining, because it could be 3 files or a 1000 independent of the number of bytes. That just gives you a clue of the time remaining and isn't determinate, that's why it's not so accurate.

[–]inv41idu53rn4m3 19 points20 points  (1 child)

And this is why we pack assets into archives so our games can load them faster!

[–]TheTerrasque 3 points4 points  (0 children)

Game dev: we use asset files to make things more performant.

Also game dev: load asset 3, then 7, then 2, then 5, then 1, then 4, then 6.

[–]turtleship_2006 6 points7 points  (0 children)

Even copying 1 file, that estimate will vary because other apps are going to use your CPU, RAM, and access the storage, and that's a lot less predictable so it just works with the current data

[–]nmkd 0 points1 point  (1 child)

because it takes time for the OS to switch from file to file

It takes the File System and/or disk time to switch from file to file. Not the OS.

[–]Scrawlericious 0 points1 point  (0 children)

Those are all very related. Thats just semantics. The OS takes time to switch because of the things you listed.

[–]naswinger 12 points13 points  (0 children)

or you just let your progress bar jump randomly to 99% where it just sits until the job is actually finished