Hacking [Question] Wii U Disks read speeds VS Loadiine games on high speed sd cards

ANTONIOPS

Well-Known Member
OP
Member
Joined
Jan 15, 2016
Messages
126
Trophies
0
Age
30
XP
840
Country
Spain
My question :

Why do some games on Wii U disks with almost zero IOPS and ~22MB/s of sequential read speeds load faster than some dumped games running on high class, god-like SD cards with crazy IOPS, (bottlenecked by the SD slot specs), but still with higher sequential and random read speeds than a Wii U disk?

Is this problem software related?


I've been asking this to myself for ages and now I feel bad for not knowing it, very bad, like putting a flapping chicken inside my pants.:blink::wacko:


I hope you can answer this correctly (or not):evil:

Thanks and have a great life:grog:
 

ARVI80

Well-Known Member
Member
Joined
Feb 25, 2016
Messages
192
Trophies
0
Age
42
Location
UK
XP
296
Country
Pretty much answered your own question their buddy.
Its down to hardware and formatting.
 

ANTONIOPS

Well-Known Member
OP
Member
Joined
Jan 15, 2016
Messages
126
Trophies
0
Age
30
XP
840
Country
Spain
Pretty much answered your own question their buddy.
Its down to hardware and formatting.

So how can some dumped games take minutes to load on SDs that are able to use the full bandwith of the SD slot (faster than the Wii U Optical Disc) no matter how you format or change the cluster size?

Shouldn't those dumped games take the same or even less time to load?
 

ARVI80

Well-Known Member
Member
Joined
Feb 25, 2016
Messages
192
Trophies
0
Age
42
Location
UK
XP
296
Country
So how can some dumped games take minutes to load on SDs that are able to use the full bandwith of the SD slot (faster than the Wii U Optical Disc) no matter how you format or change the cluster size?

Shouldn't those dumped games take the same or even less time to load?
Depends on the size of files and structure of the game.

The File Allocation Table (FAT), is an index table statically allocated when formatted. The table containes entries for each cluster and each entry contains the number of the next cluster in the file or marks the end of file, special reserved areas or unused disk space. The root directory contains the number of the first cluster of each file in that directory. The os can chain the clusters until the end of the file is reached by looking up the cluster number of each part of the fat disk.

I hope this makes sense and clears things up a little. This is the most simplistic explanation I can offer without having to go into masses amount of information, I find this subject hard to explain due to the complexities, fundamentals and history involved.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    Maq47 @ Maq47: @BORTZ sorry, not sorry. xD https://i.imgur.com/C0IOqpt.png