PMS process is always around 100% CPU: % is shown in activity monitor (25% of global CPU for my core i5). By “always” I mean that the server is just doing nothing at that time: no scanning, no indexing, no user connected, no transcoding,…
I have noticed that when I stop the DLNA server (and stop/start PMS), %CPU is below 5% for a minute or so before moving up to 100%. If I stop upnp service on my router and have DLNA activated, I have more or less the same behavior. If I stop both DLNA and upnp service, the %CPU stays low a bit longer but still moves finally up to 100%.
Provided logs is with DLNA activated.
I have to revert to version 1.13.8 to come back to a “normal” behavior, w/o high permanent CPU usage.
first, you must be sure your PMS is configured with a manual TCP for remote access, unless it will try to use upnp to register the default port (32400) in your router
Then you must deactivate upnp on your router
You can let DLNA on in your PMS
Now I don’t have permanent high CPU with PMS
…Hope Plex team will still fix the bug that seems to be related with the upnp protocol management
the upnp workaround is not permanent.
The day after (I never turn off my PMS) the high CPU load is back.
NB/ I have manual port forwarding but I have kept DLNA activated on PMS. I think it could be linked to DLNA which also uses upnp.
If you have UPnP turned off on your router it’s highly likely that you have another issue. All users experiencing high CPU usage of PMS when UPnP is enabled on a router running miniupnpd (mostly routers based on Openwrt, but some others) have seen the problem permanently solved by disabling UPnP.
You’re correct that DLNA is associated with UPnP, but simply having DLNA enabled on PMS will not cause the UPnP bug to trigger. Having DLNA enabled in PMS does, however, significantly increase CPU and memory utilisation in my experience. Don’t leave it turned on unless you need it.
