It's funny how similar issues between hdd/ssd streaming are. From the GDC spiderman presentation there was constant struggle to optimize format being streamed and avoid seeks. i.e. some asset would be copied to many streamable blocks to avoid seeks. Duplication causes install size to grow. Once asset was copied "too many times" those assets were promoted to something that is just always cached in ram to save disk space.
We likely will have similar things implemented in ssd streaming. Lump things together to read more optimally. Always cache often used/small items in ram cache to make streaming solution more optimal. It's not like fast ssd removes the need for smart datastructures and packaging.
We likely will have similar things implemented in ssd streaming. Lump things together to read more optimally. Always cache often used/small items in ram cache to make streaming solution more optimal. It's not like fast ssd removes the need for smart datastructures and packaging.
Last edited: