@hamzaaa1988 About wm throwing data though.
No, since the data is cached to disk, you can safely disable the “library/cache saving branch” without losing that data on disk. All wm data however that is in memory, is dumped. So RAM is freed somewhat, though new data is written to the memory, with the “disk cache” that’s loaded with the next branch. You do gain loads of memory back, since not all outputs are saved with the library usually. In a nutshell, you only have to keep the data you’re using currently, rest is dumped when you disable a branch.
That said, MAKE SURE you disable the “library output” once its built, along with all nodes that came before. I’ve noticed that outputs save placeholder data even if nothing is connected to them, so your cache may get corrupted on build if it remains enabled, rendering the next branch blank since the source library is overwritten with blank data…
This is why the “disable parameter suggestion” exists in the first place.