I’m sure it could. Potential is massive. But so is Graphene over silicon. But we haven’t seen Graphene make it’s debut since it’s discovery a decade or so ago. And that’s sort of what the discussions have been about. The potential is great but we have to see it in production and out for us to really validate it.
You could use fast NVME drive internally and an 'external' extra storage that could be slower and the system could cache onto the fast NVME drive. External storage could be anything from HDD to SSD to flash carts and needn't be external to the case. ReRAM isn't necessary to solve the problem you want solved.
I'm not so convinced. 25.6 GB/s is paltry BW versus the system RAM while 4 GB/s is already enough for a paradigm shift in gameplay as discussed in the SSD debate. 25 GB/s isn't going to make the difference between what 4 GB/s and what ReRAM could do save maybe some super-fringe cases dealing with absolutely MASSIVE data sets that fill your drive up with 500 GB/s games. Low latency would make streaming content easier and allow a little more in RAM thanks to less need to prefetch, but it won't fundamentally change what can be done. And remember, if we are rendering efficiently we don't need much data at all, as per Sebbbi's maths on tiled textures.
I would like 2x2080ti power on the next gen consoles.2080Ti of gpu power in next gen would be nice
I have a trash Windows tablet. Literally the free ones that ISPs give you as an incentive to switch sometimes. It's older, shipped with Windows 8 and I upgraded it to 10. Uninstalled all the bloatware, only have Netflix and Nook installed on it. It has a slow Atom Z3735F and a slower 32GB eMMC drive. Cold boots to the lock screen in 8-10 seconds. I think the current generation of consoles could boot faster if that was a design priority. It simply isn't.
That would make the newer consoles more like older ones, like Neogeo or SNES, where you had a tiny amount of RAM, but fast storage. Except in this case, games would be installed onto fast system storage instead of stored on external carts. It would be pretty interesting if Sony went this route, and MS delivered a console based on current design trends.
The benefit is when you hit a scenario where you data sets are much larger than system memory and I/O becomes a bottleneck. So we're talking data sets that are 32GB in size or greater. In which loading it into memory would limit the amount of system memory usage for the actual processing. I'd say it's becomes more useful as the data footprint increases in size. So 8K resolution for instance if you're looking at graphics. This is where ReRAM may start to be useful to have around. Very useful for cameras for instance, taking pictures/recordings at 8K with instant playback etc. Or 4K recordings (longer than 30s) to share might be another alternative for console; writing the results to ReRAM in realtime with playback, before passing it down to hard storage at a later time.
I can't talk about what I don't know. It's a good position to come in with some skepticism because it takes a while for things to change.
Yea I know it's written in Rust and they made some changes to how the OS works (URLs over filenames) I just thought it would be easier to explain it that way.
High res Megatextures everywhere. Could stream data around player form HD to SSD / ReRAM, and from there to GPU for what ends up actually visible on screen.
Megatextures only need a small read rate and RAM footprint. They benefit from low latency storage and/or RAM caching. If the drive if fast enough, you don't need to cache much in RAM, but with SSDs, a few GBs of RAM storing tiled data should be ample cache.