Originally Posted by bd2003
I'm not quite sure what you're trying to say. Are you saying that you believe part of the 3GB reserved for the X1 OS will be used to cache a recently played game from the 5GB partition?
It isn't so much caching like we normally see (i.e. caching of the executable the way Win7/8 does) as it is saving the memory state when you left the game, which changes the nature of our idea of "save games". For example, you're playing Dead Rising 3 solo and get an invite to Battlefield 4. Instead of the old notion of having to stop and save your game, go to the dashboard, then load BF4, you basically just load BF4... and then as DR3 is being left, it caches out the information it needs to a temporary space of memory. You play BF4 for a while, decide to go back to DR3, and the system can quickly load the executable for the game from HDD, load the suspended state of that game from the reserved space, then load in the resources for the game accordingly so you're changing games VERY quickly rather than the usual dashboard, load game, dig through menu, load save game method. The Jaguar architecture both the next-gen systems are using is actually designed for that kind of fast-swapping functionality.
Now, we KNOW that they're doing this kind of suspend/resume method on both of the next-gen systems because both have said so. As to the actual mechanics of that in the memory, we can't say. However, it does make sense that this 3gb reserved space could be used for that feature. Then all you have to do is have it clear out the cache on a timetable to the HDD when that suspend state isn't needed. Smartphones use this method right now to quickly change apps and resume apps where you left off. Of course, the other possibility is that they have a separate cache space allocated outside of the 3gb/5gb split (since we don't actually know the full details on that). That cache space for suspend/resume really wouldn't have to be big, since it's basically having to deal with file sizes roughly akin to save game files on consoles now (so you could have like 20mb allocated for that and get suspend states for all your games and apps in memory intelligently as you load them in/out). Then from a system architecture standpoint, you just have a slight amount of reserve power built into the HDD so that the cache clear could be completed if the system loses power (which HDDs in PC actually have now to prevent data loss from brownouts). Alternately, you also have an automatic cache clear occur when the system is in its low power mode for a defined length of time or, in the case of a complete shutdown, clear the cache during that. Windows 8's fast resume function is actually very similar to this, except dealing with the suspend state of the entire memory footprint rather than just the app's suspend data. A better example would be the Win8 kernel on Windows Phones right now, which can multitask between apps using lower powered CPUs than other phones using suspend/resume states shuffled between system ram and onboard storage ram.
The above is why I believe part of that 3gb reservation could be used in such a way, especially when you consider that Xbox One will be using a pared-down purpose-built version of the Win8 kernel on the OS side, which means it would have a smaller footprint than Win8 on the PC.