If I have 14GB of available memory, and the total filesize of

>>59495517
Because it's more efficient not to. Virtual Memory is a thing, and it would take ages to read 8GB off the disk onto RAM.

>>59495517

find /path/to/game -exec dd if={} of=/dev/null bs=1M

This reads all files contained in the directory, and in turn causes them to be cached by the kernel.
Just put it in the shell script that launches your game.

>>59495517
the entire .EXE itself is mapped into RAM.

>>59495654
Correction:

find /path/to/game -type f -exec dd if={} of=/dev/null bs=1M \;

>>59495626
If an SSD has a read speed of 500MB/s, shouldn't it only take 16 seconds for an 8GB game to fully load to RAM?
That's about the load time of a modern game anyway.

>>59495660
Thanks, I'll give it a try.

>>59495655
The .exe is only a small part of most modern games though.

>>59495788
Just use a ramdisk, also what if some of the files are compressed? you don't know for sure how big the entire game file is.

What's wrong with a ramdisk?

>>59495807
It's an inefficient way of using your RAM. The game will see it as a standard drive, so it will move its files from one section of the memory to another when it needs to load them.

If a game requires 4GB of RAM + 8GB of storage, you will need at least 12GB of RAM.
If the game would load it's entire content onto the RAM from the start, it would only need 8GB, plus it wouldn't be needlessly moving data from one part of the RAM to another.