I think that this is a problem that should be further discussed, even though it seems to be recognized on Reddit or other online gaming communities. While it does affect gaming the most, since it impacts frametimes dramatically, I am sure it also impacts other workflows.
So what is the problem?
As you are using Windows 10, it caches lots of stuff into RAM. Some things can be useful, some are quite surprising and exaggerate. As an example, Blizzard has an application hub that hosts their game catalog, Blizzard BattleNet something something. It also happens to serve as a social platform where one can chat with people, and it will also update your games. A simple start of this application resulted in Windows caching in 700MB (!!!!) files from games I didn't touch in months. If one game gets updated, files from that game will land in RAM and stay there for ages, in fact, I've yet to see them purged when you start an actual game.
This leads to a situation where after a few hours of Windows using, you will get 8-10GB of cached files into RAM. I would normally don't care - if this would not cause performance issues. The problem is, it does, and the problems are quite serious. Assassin's Creed Origins for example is barely playable, a stuttering mess if you start it with all of these files cached. You will get almost non-stop disk activity, and frametimes will be all over the place, the gameplay will be full of hitching.
As simple releasing of Standby List RAM from RAMMAP or reboot will quickly fix this and allow you to play normally, but I don't think that a user should be expected to manage RAM more efficiently than Windows. In fact, this is the first time I'm seeing Windows being so bad at this.
Another strange thing is that this seems to be a consequence of Windows trying to both avoid using the HDD to page but also cache lots of stuff and keep it there. It would rather fill the whole RAM instead of using a bit of pagefile, if HWinfo64 readings are correct.
Image below is during Assassin's Creed Origins, with the game hitching all the time as RAM "runs out", i.e. is populated with useless files from games I didn't run in months.
Again, I don't mind RAM being used, but Windows HAS to understand when to stop, when to release cache, when NOT to cache files that are almost 1GB and also not get tricked by an automatic update - when the game itself was not launched in 3 months. I'd rather just see Windows automatically releasing cached RAM if a 3D game is detected, if finesse is impossible.