High CPU and High Temp From the Start of Recording

Beta Community DVR Beta
#1

Hi,

I have a QNAP TS-670 Pro with DIY upgraded 8cores Intel CPU, i7-3770S CPU @ 3.10GHz and 16GB RAM. I have been using this NAS for 3 years, it rarely spikes more than 50% CPU and average temp is at 43c. After running the new Channel DVR for a week; now, everytime, just 2 minutes after any recording starts, NAS’S CPU spikes up between 50% to 70%, and temp goes as high as 67c. QNAP OS would auto-shutdown the system if it reaches 70c. The fan would go wild and noisy to keep the system down. The CPU would kind of tone down after 40 to 50 minutes of recording.

First, I want to understand what sorts of background task is Channel DVR doing to spike high CPU. Is it doing any encoding. Before Channel DVR, I used to have Plex DVR to record shows at the same time (Now, I stopped the Plex DVR recording completely right after I enable Channel DVR. So, it’s just Channel DVR doing recording alone), and Plex DVR CPU makes my QNAP NAS overall CPU around 7% with temp around 48C.

2nd, am I configure Channel DVR incorrectly? Is it doing any encoding in the background? Plex DVR recorded the TV shows directly from HDHomerun Extend without doing any conversion, therefore, the file is always in .ts format. I noticed Channel DVR record the shows in MPG. Is it why the mpeg file conversion causing high CPU? or something else? Is there anyway we can lower the CPU utilization? To have QNAP NAS to reach close to 70C everyday would make the Channel DVR unusable for me. I cannot afford to have my NAS to be shutdown at anytime.

Right now, I do not even dare to try Web Player while it’s doing recording because it would stress the CPU to the max.

Please advise any possible solution.

OSQNAP TS-670 Pro
Linux
(kernel: 3.12.6)
CPU
8 cores / Intel® Core™ i7-3770S CPU @ 3.10GHz
load averages: 0.25 0.46 0.52
RAM16.72 GB
78.8% free

Thanks
Rog

#2

Not sure why you’re seeing so much cpu usage… the DVR does not do any encoding while recording. The mpg file contains the raw video data coming directly from the HDHR.

Can you look at the activity monitor while recording is happening? Or SSH in and run top or ps aux to see what is using CPU. I would be surprised if it’s the channels-dvr process.

Do you have Plex pointed at your DVR recordings? Perhaps it’s going crazy scanning your library over and over while the recordings are happening.

#3

Also if you can post the entries from the Log from around when a recording starts, that would be helpful.

#4

Ok. I have done more log digging after seeing your replies. You are correct, the recording is not causing the CPU spike. But, I noticed that every time when it does the “Commercial Detection” after recording ends, I get a warning from QNAP that the temp is exceeding 60C. The Commercial Detection took about 9 minutes to run. Please see the DVR log and QNAP log below:

DVR Log:
2017/05/24 18:00:02 [DVR] Running commercial detection on file 18 (TV/Eyewitness News 5:00PM/2017-05-24-1700 Eyewitness News 5:00PM 2004-10-25.mpg)
2017/05/24 18:02:48 [DVR] Commercial detection finished with 10 markers.
2017/05/24 18:02:49 [DVR] Processing file-19: TV/NBC 4 News at 5pm/2017-05-24-1700 NBC 4 News at 5pm 2011-08-01.mpg
2017/05/24 18:02:49 [DVR] Running commercial detection on file 19 (TV/NBC 4 News at 5pm/2017-05-24-1700 NBC 4 News at 5pm 2011-08-01.mpg)
2017/05/24 18:08:56 [DVR] Commercial detection finished with 14 markers.

QNAP Log:
Warning 05/24/2017 06:09:02 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

Should I disable commercial detection? I really like this feature, it’s one of the best and most competitive features of DVR software. I really hope I don’t have to. Please advise.

#5

Can you post the output of http://x.x.x.x:8089/dvr/files/19/comskip.ini (replace x.x.x.x with IP of your NAS)

#6

Here is more log about high temp from my QNAP. Please note they are all few minutes right after recording stopped. I cannot scroll up more for the DVR log. Where is the complete DVR log located in QNAP?

QNAP System Log:
Warning 05/24/2017 06:09:02 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

Warning 05/24/2017 04:06:22 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

Warning 05/23/2017 05:05:45 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

Warning 05/23/2017 04:04:35 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

Warning 05/22/2017 11:04:44 PM System 127.0.0.1 localhost The system temperature has exceeded the threshold (60ºC). If the temperature go above 70ºC the system will be shut down.

#7

use_existing_logo_file=0
verbose=10
logo_fraction=0.39
delete_logo_file=1
output_vdr=1
output_edl=1
output_ffmeta=1
output_ffsplit=1
thread_count=4

#8

Thanks, this is due to a change from a few days ago to try to use more than one core for commercial detection. I am going to change it back to how it was before.

#9

Thanks for your quick triage. When can I expect an revised version?

Much appreciated

#10

Should be ready in an hour or so

#11

You can run this command in a terminal to update immediately:

curl -XPUT http://x.x.x.x:8089/updater/check/2017.05.25.2249

#12

Wow. So quick. I’m really impressed. Saw a lot of people mentioned the best support. Now, I’m convinced. Thanks much. I’m going to try. Well let you know the result.

#13

Hi, I have just updated to 2249 version. But looks like the comskip.ini setting is still the same, using 4 Threads.

Below is the latest comskip.ini:
use_existing_logo_file=0
verbose=10
logo_fraction=0.39
delete_logo_file=1
output_vdr=1
output_edl=1
output_ffmeta=1
output_ffsplit=1
thread_count=4

Version
2017.05.25.2249
Up to date!
Uptime3 minutes
Started Today at 4:39 PM

#14

That’s expected. Will be 1 on newer recordings.

#15

Does that mean I have delete my old passes and create the new passes to take the “1” thread setting? Or the next new recording on the existing passes will take the “1” thread setting?

BTW, for some reason, the ini file http://x.x.x.x:8089/dvr/files/19/comskip.ini no longer exists. Did it move to some other directory or it got renamed?

Thanks again,

#16

You don’t need to do anything. The issue has been fixed and the next time comskip runs it will only use one CPU.

#17

Basically every new recording gets its own comskip.ini. That one was for recording 19 (NBC 4 News), which you probably deleted after watching.

New recordings will have different numbers and will use the new settings.

#18

Yes. I can confirm it’s using 1 thread based on the individual CPU graph chart. The Temp was at 50c when commercial detection was running. Much better. Thanks.

1 Like