My experience with the beta build was that on startup the dotnet Linux server indeed uses more physical memory than the Mono builds before. But, after a while memory usage goes down and, more importantly, stays down, even under heavy system usage. So, perhaps after a couple of hours you may look again and may get positively surprised. Let’s hope so…
All good on Ubuntu 20.04 LTS (rebooted after update). Definitely seems zipper.
(Smoke me a kipper, I'll be back for breakfast!)
Have to hand it to Mark Cole at Antipodes.
He helped me with my older Edge unit to get it updated to their new v3.1, a version it was never designed for and envisaged running.
But it’s done and now running build 846 very happily indeed.
Nice job all round to Antipodes and Roon teams for pulling this one off successfully.
The upgrade was flawless and there ARE noticeable performance improvements while navigating, however it’s still slow.
Specifically, rebooting the docker container - it takes 3 seconds only for the client to detect the server. However, it takes 2 minutes and 41 seconds for the client to move on past the Roon logo to the main screen at startup.
The navigation is still not snappy either. Before hearing this fix was coming I went to the extreme step of backing up my database and reimporting to a new one - which didn’t help.
There’s something funny still wrong - perhaps it’s just me. I have a 12GB database of which about 9GB is images. 120k tracks - so not the smallest, but not the biggest either.
And I might add, this wasn’t always the case, it did used to be snappy - I’m not sure when that changed, but figure it was an update at some point.
If it would help troubleshoot, I could spin this up in a VM, or a dedicated machine.
I have tons of RAM, Fast Disk and CPU at my disposal - these are not issues in this case.