@Charm8er With lack of memory enough to hold data, wm swapped a lot of data to disk. It’s that paged data that’s causing issues with slowdowns, along with OS being paged to disk as well due to memory not being available. WM dumping data seems logical in that case, especially if you have any form of “memory conservation” enabled in your project settings.
What you need to learn, is to break your project down into parts, spread it across multiple stages. And learn some optimization techniques if you want to go that high resolution. If you’re hitting memory walls with 128GB RAM, you’re going to be in deeper trouble when you start with materials.
Try the method I described in this tutorial project, but with multiple wm projects. Link them through library caches. This way you’re only holding parts of data while you’re building, saving memory. Great general optimization technique (I built terrains with 16gb memory, on a laptop, for clients, under deadlines using this technique once upon a time).
Besides that, try using fewer nodes per project if you wanna go that huge on resolution. I don’t know what kind of organic details you want, but that high resolution is impractical imho, people use all kinds of techniques that are much more art-directable than brute forcing everything in one go. What’s the point of these granular details if you can’t even make edits to it after builds…?