I've been trying to track down the cause of numerous slowdowns in Adobe Lightroom Classic, and I've stumbled across a surprising interaction between Process Lasso and Lightroom.
Process Lasso Pro: 19.0.0.94
Lightroom Classic 15.6
Windows 11 Pro
AMD Ryzen 9950x
192 GB RAM, 149 GB free
RTX 5080
Symptoms: With the Process Lasso GUI open, the UI of Lightroom is extremely laggy. Even launching the preferences window can take 6 or 7 seconds. Substantial delays switching from one item to another in both the Library view and the Develop view (Develop noticeably worse). While Lightroom Classic is known to have performance issues on Windows, this goes well beyond the normal. This is after a fresh reboot, loading a catalog, and doing no editing work. Just UI navigation.
Experiments: tested with Probalance enabled/disabled. Tested different process priorities for Lightroom, as well as exploring restricting it to different affinities and sets. No change (my default is to let Lightroom access all CPU resources).
Closing the Process Lasso window and letting it remain as a tray process made a substantial difference in the UI performance of Lightroom (improved). Existing the Process Lasso program entirely (leaving the governor running) further improved performance to baseline. Did not test with the governor disabled.
It appears that ProcessLasso's UI is constantly readying Lightroom's main thread. Lightroom Classic itself is a bit of a mess internally, doing lots of synchronous operations on the main UI thread and it seems that every time Lightroom wakes up it's triggering some of those actions. That's dumb on Adobe's part and a performance annoyance of its own, but Process Lasso seems to be throwing fuel on the fire.
I much prefer to keep Process Lasso open on a second monitor. I'm often switching between various workloads (editing, development, work, etc) and so I frequently tweak things based on what I'm currently doing. It would be nice to be able to continue to do that and monitor my resources without it having such an impact on Lightroom.
FWIW, Lightroom seems to be the only application impacted by this (other Creative Cloud applications, like Photoshop, continue to function just fine).