very high CPU usage

[sbiddle]

I've noticed my PC has Windows Elitedesk USFF has been a little sluggish watching things lately and the web interface has been sluggish too. I've just decided to take a look at this now and the culplit seems to be NextPVRserver sucking 70% of the CPU resources.

I'm running 7.0.1.241229 and can't seem to see anything in the logs that would indicate anything and the CPU is being smashed when the system is idle - I'm not watching or recording TV at the time. Rebooting or stopping and restarting the service seems to fix this temporarily but the issue just comes back eventually after some use.

Anybody have any ideas or is there any logging I can enable which might show things?

[sub]

I've not seen any other reports of this, and a look at my systems here doesn't seem to indicate any significant CPU usage while idle.

Activities that can cause notable CPU usage:
- transcoding for watching in the web app (though ffmpeg is using the CPU)
- post recording auto transcoding (though ffmpeg is using the CPU)
- EPG update

[mvallevand]

And thumbnail, timing and comskip.

[sub]

yes, true.

[BrettB]

Anybody have any ideas or is there any logging I can enable which might show things?

You didn't give many details of your setup (beyond the fact that it is running on Windows). What tuner(s) do you have? What clients are you using? What is/are your EPG source(s)?

It would be helpful for you to simply post a set of logs generated by clicking the Log Files button on the Settings page of the web interface. Then we would be able to see the answers to all of the questions. And sub (and Martin) can often see things in the logs that typical users wouldn't notice...

[Allan]

transcoding for watching in the web app (though ffmpeg is using the CPU)

I have seen CPU usage go crazy high when starting to watch something in the web app, cancelling, and starting something else. After maybe 3 or 4 repetitions, it won't even play any more and CPU remains high until I restart NextPVR. 

If I see it again, I will save logs.

[mvallevand]

Although this is a Windows thread I also saw the high CPU trancoding ATSC that Allan saw on macOS when I first used macOS. If felt it was more macOS related since it ffmpeg was taking the CPU and it resolved after a restart so I didn't think it was a NextPVR issue.

Martin

[Allan]

I should mention that it was not ffmpeg, but dotnet, that was running hot when I observed the issue. It was, as Martin points out, on a mac.