I am a long time lover and sufferer of Roon. Reading most of the threads about Roon, I am pretty confident that there are multiple issues with Roon and moreover some of the issues arise out of the composition of your library.
This is why one person suffers from performance freezes and another doesn’t, on the same hardware.
Roon appears not to handle very large collections of streaming titles, and struggles when trying to identify unidentified albums like bootlegs, vinyl captures, and the like. It also seems not to like libraries that have lots of user tags.
My Roon server is on a 6-core 3.9Ghz i5 11500 with 32MB RAM and a PCIE 4.0 SSD and Roon chokes itself to death about 1/4 of the time with some form of database or library processing. It just grinds and grinds and grinds - CPU usage goes well above 100% -- until Roon loses its *** and loses connectivity for a second. When it’s done, back to normal, but in the interim it’s paused the music, and sometimes logged out of Tidal and Qobuz.
The differentiating feature among all users who have different issues or no issues is their library. That’s Roon’s database architecture and scheduled processes...sensitive to some library issues and not others!
This is where Rock and Roon Nucleus are at a disadvantage - the user can't see the resource abuse happening inside the box.