Performance Issues on Build 1683 [Ticket In]

Support
1

It’s looking like build 1683 is back to memory usage steadily increasing without dropping back down. Build 1680 would increase then decrease, as expected, but build 1683 doesn’t seem to be releasing any memory.

At my last reboot a little over a week ago, b1683 was at 1.6gb and has steadily increased to 5.6gb without any drops in memory use in between. :frowning: So far, performance is still good, though today I’m noticing slightly slower discography page loading sometimes, albeit still pretty good loading within a few seconds. But, will it deteriorate like before as memory usage continues to climb like it did with 2.70?

2

Hi @Saturn94,

We’re taking a look. Thanks for the report. We’ll share more information shortly.

3

Thanks! :grinning_face::+1:

4

Hi @Saturn94,

Moving this to Support as we’ve identified the source of the pressure in logs with development. There’s now a ticket in the pipeline along with a few other accompanying minor fixes.

Since this might not make its own dedicated bullet line in Roon Software Discussion > Software Release Notes, we’ll circle back here when we expect this to be released to EA. It should be an upcoming build.

Thank you again.

5

Thank you! :+1:

6

Hello @Saturn94

One thing to add before we leave this with you.

Your observation was accurate and it went straight to development, so there is nothing further we need from you here.

If performance does start to deteriorate in the meantime, please tell us roughly when it began and how long the server had been running. A restart remains a legitimate way to clear it until the fix lands.

7

Thank you!:grinning_face:

I’ll let you know when/if performance takes a hit.:+1:

8

Hello @Saturn94

Please keep us posted on any progress here.

9

Thanks for checking in. Here’s the latest.

So far, despite memory use still being very high, higher than ever before, performance doesn’t seem to really be impacted.

I’ve avoided rebooting to see if Roonserver will eventually crash or restart on its own. So far, it has not.

10

Thanks for the update. We’ll continue to gather diagnostics remotely at regular intervals and should have captured this window.

11

Thank you! :grinning_face:

12

Hello @Saturn94

Thanks for the update, and for letting it run rather than rebooting. That is genuinely useful data.

We are going to close this thread now, since there is nothing further we need from you. Diagnostics are being collected remotely at intervals, so the window you have been holding open is already captured.

If we need anything from you as the work progresses, we will reopen this thread and post the question here.

For the fix itself, the release notes are the place to watch:

And if performance does deteriorate before then, please open a new thread with a link back to this one, and tell us roughly when it started and how long the server had been running.