Roon 2.65 - it was faster for a while, not so much after a while

Roon Software Discussion
1

First of all, thanks to the Roon team for their efforts on improving the performance and usability. I appreciate the progress they’re making. I totally understand it’s a complex product and there’s a lot of legacy involved.

With that said, there’s still a ways to go. Roon on my Nucleus+ has been agonizingly slow for me for the past couple of years, everyone once in a while it gets faster after an update, but then it reverts. The typical MO is that Roon is decent after a reboot, and then slows to a crawl within a day or so.

I upgraded to 2.65 on Monday and Roon was instantly much faster! I was excited that this was finally the breakthrough. I went back to Roon on Tuesday later afternoon and it seemed slower, but I didn’t think much of it. And then by mid-day Wednesday, Roon was very slow again. Not quite as bad as before the 2.65 upgrade, but very noticeably slower than on Monday. So I rebooted the Nucleus+ and within 15 minutes of the reboot, Roon was fast again. But now, 24 hours later, the slowdown has returned - borderline unusable.

Seems there are still lingering memory issues and needs a daily reboot to behave in a reasonable fashion. I think a great feature would be to have a “nightly reboot” setting that will restart Roon server every night.

Anyone else have this same experience?

15 Likes
3

Yes, I`ve got the same problem on my NUC:

Performance degradation on Roon Rock after prolonged uptime (ref#R761T7)

4 Likes
4

Yes same for me, was lightning at first but a few days later its slowed right down again :frowning:

1 Like
5

Some additional information would be beneficial. For example, library size, number of unidentified albums, background work schedule etc.

6

I have become used to rebooting (not re-starting) the server once every 1-2 days, esp. following changes to the library. This helps in keeping performance consistently at an acceptable level.

6 Likes
7

Roon Rock is installed on a NUC7i3 with 16GB of RAM. The database is on a 256GB SSD, and the tracks are on a 1TB HDD. The library is relatively small: 2,800 albums and 35,000 tracks, 0 unidintified. Background work is off.

8

5931 total albums and 855 are unidentified. 104,000 total tracks, and 18,600 of them are unidentified (they are live recordings/bootlegs, mainly from a handful of artists). See more at:

https://community.roonlabs.com/t/slow-response-and-playback-delays-in-roon-ref-u7s5mf/317034

9

Everyone affected should open a support ticket. It’s not normal behavior. In particular if the update didn’t help.

2 Likes
10

That’s a lot. Did you use the feature to schedule background work to a time when you don’t use it?

1 Like
11

I’ll reopen the thread so you can provide an update there.

@Atiss, nothing out of the ordinary so you should open a Support request as @Suedkiez suggested.

Anyone reading this thread, please avoid piggy-backing on someone else’s thread as similar symptoms doesn’t mean the same problem. Thanks.

12

A request has already been created.

1 Like
13

That’s a lot. Did you use the feature to schedule background work to a time when you don’t use it?

Yes, I have background work and background audio analysis scheduled for overnight.

14

OK. I’d expect that then it doesn’t try to identify the huge number when it shouldn’t. :man_shrugging: I suppose support has to continue looking for the cause in your reopened support thread.

15

I can only guess that it starts trying to identify overnight and then just keeps going instead of pausing at the end of the overnight window? I’ve said many times that there should be a flag for certain type of content, e.g. bootlegs, that should always remain unidentified, i.e. if you flag them, then Roon will never attempt to identify them.

2 Likes
16

No idea, seems possible but this would be clearly a bug and should be easy to find in the logs by support and should be easy to fix if it’s really this.

Yeah, me too :slight_smile:

2 Likes
17

Here also. Snappy and quick in beginning after a reboot but then back to the old story of slowness and in the end loosing audio endpoint. Last playtime was little over 20 hours before it stopped. I have a Nucleus One with 32gb memory

1 Like
18

Way more memory than the One could ever use. So, what size is your library?

19

81846 tracks. Why not go all in with memory? Back in the days memory was cheap. Is it a problem maximizing memory?

1 Like
20

The N1 is rated for 100k tracks and comes with 4 GB for this rated library size. And Roon OS has either enough memory or not, and in the latter case it just crashes (in which case 8 GB would be a good idea). More RAM than is needed for the library size does not speed anything up with Roon OS, it will just be unused.

32 GB won’t hurt, I think, but if a Roon database on an N1 ever needs 16 GB, it will grind to a halt for other reasons, anyway, because the library will most likely be too large for the available CPU power. In addition, the Celeron CPU in the N1 seems to be limited to max. 16 GB, anyway.

At least you can rest assured that your performance woes are not caused by too little RAM, which is something :slight_smile:

1 Like
21

I put 32GB RAM in my Nucleus+. And I upgraded the system drive as well. Total overkill for my 100K tracks. The hardware is not the issue….

1 Like