Roon is not other music library / streaming applications. Because of the interconnection within the database, it has very different demands. That’s why RoonLabs recommends a fairly recent x86 machine, and not a RaspBerry Pi which’d run other music library applications just fine as a server, and why people asked about SSDs. It’s also why you might be hitting an OpenGL bug.
It isn’t struggling with the volume of data. If you had half a million tracks, then maybe that’d be on the table.
There you go. You want to export the database, install the 32 bit, and reimport the database. Export / backup doesn’t have to be to a different drive if there’s enough room there.
I’m probably partially responsible for that, and I’m sorry I made things worse rather than better for you. The upside is that we now can assume that the problem isn’t the client machine, which could’ve been possible.
I very much understand your frustration, and I’m quite frankly amazed you stuck to Roon for this long. If that can be of any relief, the sluggishness you’re describing is emphatically not normal at all on the setup you’ve described.
Please take the time to describe your setup as extensively as possible, as @Geoff_Coupe has suggested. That’ll help everyone trying to help you. One thing that’d help at this point is having a specific model for your Sony all-in-one. Another is knowing what other software you’re running on that machine.
Seeing what you’ve described, I see a few things that could be a source of issues (in no particular order). Others will probably pick up on other, possibly more relevant stuff.
One is a completely saturated SSD, as @grossmsj put a finger on higher up. I know this sounds like basic stuff, but knowing if you’ve got a really full drive could help rule that out. You know that, we don’t.
Another is the intel bug @Geoff_Coupe mentioned. Installing either 32 bit or server might weed that out. I’d try those two in that order. Server doesn’t have to whip up a rich interface (so if the intel driver bug is what’s making your all-in-one spazz, that’s out), and is lighter on the system.
Yet another, because there’s less people using those than NASs, is that there’s some outlier issue with Naim’s SMB sharing and Roon in your particular setup. One way to test for that would be to temporarily take the Naim out of the equation (by removing the shared folder from your Roon core (within Roon, Settings - Storage - three vertical dots next to the folder, remove) and doing a library cleanup after that (library - library maintenance - clean up library, mark all three options). This is a much longer shot, and quite a bit more involved (because putting it back will mean rescanning that, and it’ll take time), so that’s what I’d try as a last resort.