Ongoing High CPU Usage for Roon Server (ref#YNNMQ8)

What’s happening?

· This is a continuation of my prior report [(ref#MNE4Y2)](https://community.roonlabs.com/t/high-cpu-usage-observed-on-roon-remote-application-ref-mne4y2/283851). The issue resumed today (same Cloudflare DNS settings). And I now see that it also sometime varies between tracks (for example two tracks off the same album, same sample rate, etc. trigger very different CPU usage on my desktop, but most tracks all seem to push the CPU towards 10+% and trigger the CPU fan to come on). All day yesterday it seemed fine, but now the problem is back.

How can we help?

· None of the above

Other options

· Other

Describe the issue

Ongoing High CPU Usage

Describe your network setup

Server, remote, and speakers all hardwired

I just discovered a possible connection: This problem is only manifesting when the Roon app is showing a scree that includes the animated bars next to the playing track. For example, in a “daily mix.” If I navigate away from that screen the CPU usage drops, even if the music keeps playing. The CPU usage will immediate spike if I return to the daily mix screen that includes the playing track.

If I go to the queue the CPU usage is high while the now playing track is in view, but drops if I scroll that track off screen.

Hi @Miles_Cowan,
Thanks for writing in to ask us about this issue. I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.

However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.

First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.

Hi Daniel:

This morning at 5:47 ET I started playing a daily mix and my CPU usage spiked to over 10% while on the daily mix screen showing all the tracks, including the animated bars next to the currently playing track.

As soon as I navigated away from the screen with the animation my CPU usage dropped to around 1%.

Thanks,
Miles

Hello @Miles_Cowan

If you paused the song so that the animated bar stopped, did the CPU spike also then stop, while still on the same page?

Yes, if I pause the track on the page with the animation the CPU usage drops then spikes again when I resume playing.

Same issue here, I don’t remember this being an issue prior to the 2.0 version. The higher CPU usage only occurs when the animated bars are going. The CPU goes from less that 1Ghz clock speed to a constant 4Ghz+ and the temps will shoot up to 60C+ from low 40C.

Can I ask what Os you using and is this using Roon app on the server itself?

Using Windows 10, Roon server / app running on my PC, not running on any other devices.

1 Like

Hey @Miles_Cowan,

Thanks for the update and for your patience!

As a next step, I’d be curious to see if the same issue occurs on a fresh database.

Let’s try a fresh database and see if your issues persist:

  • Create a Backup of your current database
  • Exit out of Roon + RoonServer (from taskbar area)
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon Server”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup (sign into Qobuz to test audio playback before restoring the backup / importing any local files)

Here is the process outlined from a Windows machine:

All Roon_old on Windows

We’ll be on standby for your reply, thank you!

Wonder if there will be any more updates on this…
Just re-installed Roon on a Mac Mini M4 Pro, 24Gb RAM - and later migrated to a Windows 11, Intel i5, 8Gb RAM box - local library no more than 1250 records. Looong time after the initial import and scan of the Library - Roon keeps eating 10%-40% CPU, was happening on both platforms.
very strange.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.