One problem seems to be related to the search-index process, an apparently memory-hogging process wherein (ostensibly) the totality of files are indexed for "faster searches." A work-around is available recommending a very, very small change in one value on one line of the registry, using regedit.
Another bug-a-boo seems to be the One-Drive application, and any of several processes that seem to want to "phone-home" with or without your permission.
Occam's Razor strongly suggests starting with the most simple and most likely issues, like all the little hitch-hiker processes that rev-up at Start-Up. Killing those before a re-start is recommended, though access to those options is limited using the WinX tools available through the Task Master.
Another of Occam's recommendations is to remember certain browsers steadily increase their use of available memory as any one session runs; and then there's the more obvious need to regularly clean a cache file.
If this problem is related to the more complicated issues, and not just a background scan or a slowed update by anti-virus, for example, you should know that it is unlikely to be related to your own physical memory. It's a relatively recent issue being experienced across the board, after very fast initial experiences immediately after upgrade.
There is increasing chatter about such issues across the tech-blogs.