[High Network Usage by RoonServer on Idle] (ref#FGYQQ8)

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

When idle, my RoonServer instance (running on a MacBookPro as a dedicated Roon server with Linux Mint installed) is downloading, on average, ~600MB per hour, or ~14GB per day (according to my Asus router's traffic meter). I've been running the same install of Roon for probably a year now and generally only add new content once/week-ish, so I'm curious why RoonServer is pulling so much data when idle.

To test that it really is Roon on that box, I killed Roon overnight and my traffic meter shows the overall bandwidth from the server going to near-zero, so I can 100% confirm that the majority of the daily ~15GB pulled by that box is 14GB coming from Roon (see screenshot). Any reason for it needing to download ~10MB/min constantly, even when idle and not streaming any music locally or via Tidal?

Describe your network setup

Asus router; Roon server and clients hardwired via ethernet through a TP-link unmanaged switch

Hi @rcrawley,

What happens if you throttle background audio analysis in Settings → Library?

In many cases, this background up- and downstream traffic is caused by Roon’s analysis service, which matches the waveform of any new files in your library with content in upstream servers to identify content and associate it with metadata automatically.

Looking through logs, we can see analysis spinning on what appear to be live concert tracks. Another test would be to temporarily de-activate your Watched Folders, so only Tidal content is accessible to Roon when in the background.

We’ll watch for a response. Thanks!

Thanks @connor. Restarting RoonServer stopped the constant download; here’s what it looked like after the restart:

So I’m guessing that the analysis being stuck on a specific live track was causing the constant bandwidth usage? If so, this bug(?) seems a bit problematic for those of us who may have bandwidth limits from our ISPs (which is what sent me down the path of finding the offending box/app).

Are you able to tell how long analysis was stuck and it was pulling 600MB/hour?

Thanks!