Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· None of these quite match
Tell us what's going on
· Last Roon app on NAS require huge amount of CPU resoiurces
Tell us about your home network
· LAN
The Roon on NAS was restarted as I updated ffmpeg7 in /bin folder.
The previous versions were started without any issue and last 2.58 has use huge amount of CPU and Write to Disks Megabytes…
Log file contain
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1146] GET to https://api.roonlabs.net/devicedb/1/images/c647bdc99346027fde33e65ab681713eb90ace09.svg timed out after 100012 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1194] GET to https://api.roonlabs.net/devicedb/1/images/771ef84041e1f2eca4a5e0bb9233e104d69458f5.svg timed out after 100010 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1156] GET to https://api.roonlabs.net/devicedb/1/images/19d36aac622529f32d55fc8a04ca82784457f455.svg timed out after 100014 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1279] GET to https://api.roonlabs.net/devicedb/1/images/31e81fa45f1e9fa4e3c2662ecf00e9757a727841.svg timed out after 100005 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1260] GET to https://api.roonlabs.net/devicedb/1/images/38e2d123259a47d126096a34f77dda79cd35afe3.svg timed out after 100009 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1306] GET to https://api.roonlabs.net/devicedb/1/images/aa4f62ba33a3d9c57afd99eac52466c7b354415c.svg timed out after 100031 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1148] GET to https://api.roonlabs.net/devicedb/1/images/162c6e4ecc5928f64573411ea86f9ce139b8aba9.svg timed out after 100055 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
01/30 10:48:57 Debug: [easyhttp] [1210] GET to https://api.roonlabs.net/devicedb/1/images/9a61c5719e4fd4d99051a30e466dc06cdcdbffa2.svg timed out after 100056 ms
01/30 10:48:57 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult
No changes was done for LAN configuration.
I hope you can fix this or explain.
After 5-10 minutes the Roon stabilized and hasn’t require CPU resources.
Regards,
Alex
When Roon restarts, it does a complete library rescan. As long as it stays down after that (in the first 5-10 minutes), you are a-ok.
1 Like
Hello @Alex_Malyshev,
Thanks for the additional details.
Based on what you’ve shared, this behavior does not indicate a defect in Roon itself. Roon can periodically perform background work (library maintenance, metadata refresh, device DB updates, cache rebuilding), and these tasks may be triggered at times other than a restart.
On systems that are below or close to Roon’s minimum recommended CPU performance, such background activity can result in noticeable spikes in CPU usage and disk I/O.
In your case, an AMD Ryzen R1600–class CPU is below what we generally recommend for sustained Roon Server workloads, particularly on NAS-based installations. With this class of processor, temporary performance saturation during background tasks is expected and unavoidable.
Since:
- CPU usage eventually returns to normal
- Roon continues operating correctly afterward
we don’t currently see this as a software malfunction.
If you continue to see prolonged or constant high CPU usage that does not settle over time, please let us know and we can take a closer look. Otherwise, improving performance would require stronger CPU resources or moving the Roon Server to a system that meets our recommended specifications.
1 Like
@Alex_Malyshev given what you report here, if the information is still the same, your NAS has enough power for your collection. What you are seeing is normal upon a reboot.
Of course that depends upon what other uses you have for that NAS (mine is dedicated) because you are reporting:
Dedicated to music use? (Yes/No)
No
I think something wrong with people here.
@vadim could you close this topic please.