I’ve recently noticed my Plex server using 30% of the CPU constantly.
I run a server on Intel NUC - 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz 2.80 GHz, 32gb RAM.
Nothing is running in the background (no maintenance or anything).
I noticed that if I end the task in task manager, and restart it, it won’t burn through the CPU until I play 1 video or add a file. After that, it is stuck in a loop buring approx 30% CPU.
Oh and I have to shut it down in the task manager if i just quit it from the taskbar it doesn’t actually shut down.
I don’t know how long has this been going on but I noticed recently because the fan in NUC is always on (which it wasn’t before) no, it is not dirty or anything and the room is airconditioned so external heat shouldn’t be the issue either.
I was looking through threads and only found old (3+ years) issues that seem irrelevant.
Are you downloading directly into the media folders to which your Plex libraries have been directed?
If you do, are periodic and/or automatic library updates in Plex activated?
If they are, try disabling them for now.
Which can mean that each additional downloaded byte will trigger another scan by the server.
I recommend that you use a different folder, which is located completely outside the folders of your Plex library, for downloading, unpacking, and renaming to meet Plex requirements.
Only after all steps have been performed to prepare your media files, you should move them to the Plex media folders.
Doing so will also tremendously help to avoid mismatches in Plex.
But why would this start happening in the last 2 weeks and not before?
It makes no sense, I’ve been downloading the same way all the time without any issues. And why would after the download is complete there be additional “bytes” that doesn’t make sense.
Also a “scan” shows up on the dashboard, which in my case doesn’t happen
I am talking about the time, during which the download is performed. Particularly when using Torrent a client, downloads can consist of several streams which fill up many files (or different parts of files).
I cannot tell.
Start by trying the steps and practises I outlined above, to see if they have any effect.
I had kind of expected to see something like a stuck transcoder process, and in a case like that Process Explorer will show you the command line arguments which can help you spot bad files.
