They are literally the most data intensive software you have in terms of UX. Your movies, music, documents, and even non-served databases are all browsable on low bandwidth low IOPS devices just fine with sophisticated algorithms.
Your load times for a level of Call of Duty are always reflective of how long it takes to get texture data off the disk and into vram, and that is constantly being hammered. It sometimes even causes texture popping on crappy notebook hard drives.
I have 256GB SSDs in my desktop and notebook (with intents to find a nice 1TB drive next year, since we are at the tail end of SATA3) and my Steam library on my desktop is 176GB by itself.
My OS on its own (Arch) discounting pacman provided games (0ad, doom3bfg, darkplaces, doom, etc) is around 6GB, and most of that is Qt doc, Python2 site packages, 300MB of wallpapers, and 600MB of locale.
Not only is load time reflected by the time it takes for texture data to be copied into vram, but what constitute reasonable load time is to a degree based on developer platforms and those have a tendency to use above average hardware. If in the past 10s load time was maximum, that number will now be more likely based on SSD speeds rather than HDD.
Your load times for a level of Call of Duty are always reflective of how long it takes to get texture data off the disk and into vram, and that is constantly being hammered. It sometimes even causes texture popping on crappy notebook hard drives.
I have 256GB SSDs in my desktop and notebook (with intents to find a nice 1TB drive next year, since we are at the tail end of SATA3) and my Steam library on my desktop is 176GB by itself.
My OS on its own (Arch) discounting pacman provided games (0ad, doom3bfg, darkplaces, doom, etc) is around 6GB, and most of that is Qt doc, Python2 site packages, 300MB of wallpapers, and 600MB of locale.