OK, allow me to go off topic and rant about something for a minute. I tried the new Edge browser. First thing I noticed--it scrolls "better" on my PC. Smoother scrolling, with seemingly a higher "refresh rate" than Chrome. That makes no sense, right? And yet, the difference is clear as day.
Mind you, this is something that crops up every now and then on my main laptop. I don't have a slow machine--8th gen Core i7 with 16GB RAM and PCIE storage, discrete graphics, etc. But inevitably after a few months, certain apps (primarily Chrome and Office, so like 80% of my usage) seem to get "slow" at scrolling or refreshing content on the screen. I thought the culprit may have been some Logitech mouse/keyboard drivers, so I killed those and removed any Logi extensions from Chrome. Didn't fix it. The only way to fix it (at least for a few months) is to completely "refresh" my PC, lose all my apps, and start from scratch (and not install any drivers outside of Windows Update.)
Why is this so hard? I'm pretty convinced my next machine is a Mac.
Look up Memory Management and Large Pages or Huge Pages. It's a Group Policy setting, I believe, to enable them.
Same thing happens to mining software that uses a large expanse of Virtual Memory. Page mappings become fragmented, and slow everything down, once that happens. This is not "paging" per se, meaning moving pages of memory between RAM and backing store, or vice-versa, rather, that the data-structures for these virtual-to-physical mappings, become fragmented heavily, so that, say, copying a large area (screen scrolling, and displaying images, etc.), becomes slower, because every 4MB page, you need to re-looking the mapping for the next page. This happens semi-transparently in the processor, and is partially also handled in software (page fault handler).
It's vaguely similar to the internal block fragmentation that you don't get to see, inside an SSD (mapping tables), only, this has to do with the mappings between a processes' virtual address space, and physical RAM (and additionally, any space used in the backing store, aka "pagefile").