Well then you'll be thrilled to hear about NiER: Automata for the Nintendo Switch Family of Systems™!
Size on PS4/Steam: 47GB
Size on Switch: 11GB
It even got a physical release on a Switch cartridge and everything. You'd be surprised what can be done with compression and the removal of duplicate assets. Plus if I'm not mistaken there's evidence that Drake has a dedicated decompression system, meaning compression might be utilized to even greater effect on the next Switch without hurting performance/fidelity.
(if I'm wrong about the compression stuff then someone smart please correct me )
Just wanted to use your post as a springboard for me being in a goober mood for some
random blabbering, yeaaaa.
Alright, the related part is, PS4 needs such duplicating of assets is because of the mechanical Hard Disk Drive.
How slow is accessing random data on a modern HDD? I'm seeing a range of 10-15 milliseconds for typical (ie not the really high RPM ones) HDDs, so let's go with that .
For comparison:
NAND flash based storage is usually in the two to three digit
microsecond range. It's kind of funny; in one context, I can say that the shift from HDDs to NAND flash internal storage was extremely beneficial for the user experience. In another context, I can also say that NAND flash is still dreadfully unresponsive. And they're both true.
As for (regular/LPDDR) RAM these days, I've seen a range of ~90's to ~150's
nanoseconds. (the ~150's Van Gogh/Steam Deck, what the hell? On Intel's side, Ice Lake's ~130 and Tiger Lake's just under 100...)
GDDR (or more specifically, the PS5 chip)'s ~240
nanoseconds
Typical L3 cache clocks in maybe 10-15
nanoseconds?
L2 cache you probably want in the 3-5
nanoseconds range?
And L1 cache's ~1
nanosecond?
Time for fun with timescales!
Imagine if you will, a CPU chugging along, doing work, retrieving data, all that jazz, as a person (you) jogging.
Now notice how I italicize the prefixes (nano/micro) above? Let's... replace them. Normalize such that 1 ns = 1 s.
Doot doot doot
You're number crunching/jogging along just fine, but then, you need to retrieve some data.
You find what you need in L1 cache (~1 -second)? Your stride ain't broken! You keep on cruising along.
Miss in L1, but find what you need in L2 (~3-5 -seconds)? You stumbled, but manage to recover. It takes several steps to get back to regular speed, so you lost a tiny bit of time.
Miss in L1 & L2, but find it in L3 (~10-15 -seconds)? You tripped! But the fall wasn't bad; maybe you got lucky in breaking it. A few breaths later, you gather yourself and get back into it.
Miss in all your cache and have to go to RAM (regular/LPDDR; so ~90-150 seconds)? You tripped and fell flat on your face! Or you crashed into something and hit the ground! You roll around in pain for a bit and take a breather before resuming the jog.
Alternatively...
Miss in all your cache and have to go to RAM (PS5; so ~240 seconds?) You tripped or crashed into something and hit the ground like above! But while you're still on the ground, someone else comes running along and trips over
you! And possibly lands on you! That kick to your side and potentially another body landing on you extends the recovery time.
Miss in everything up to RAM and need to go hit up your (NAND flash-based) internal storage (let's go with... 100,000 seconds?) That's...close to 28 hours. You step off to the side and set up camp, resuming the jog the next day.
Alternatively...
Miss in everything up to RAM and need to go hit up your (HDD) internal storage (let's go with... 10,000,000 seconds?) Close to 116 days? So near 4 months? So uh, you suddenly stop and decide to hibernate through a little more than a season?
Alright, so that metaphor got extended a bit too far there. But sticking with this...
What if I were to suggest to try visualizing the NG and the PS5's CPUs as in a
sort of a, but not quite Tortoise and the Hare situation?
Surely you people know what scenario(s) I'm alluding to/what direction I'm going with here; I'm so very scrutable.