Right, thank you; I have a lot to digest now.
Hello again,
Problem radically solved!
Mainboard Supermicro X10SLH-F with Xeon E3 1286 at 3.7GHz 8 core, 32GB ECC ram. Disks are the same.
Transcoding 1080p to 328p, cpu at 10%!
But the most amazing is that total power into the PC is 26W, even transcoding! I thought that HP microserver N54L, with 50 W at idle was low power. This is really incredible.
Thank you for your support, I can enjoy Plex on the road now.
Best regards,
jss
Let me know you need help setting up Hardware Transcoding, as that might help as well when Transcoding is needed.
Yes please, by all means, thank you for being so thoughtful and helpful.
I didn’t know there was any special settings, I’ve just:
Transcoder quality: automatic
Transcoder temporary directory: blank
Transcoder default throttle buffer: 60
Background transcoding x264 preset: Fast
Maximum simultaneous video transcode: 4
Now, I know that my cpu does QuickSync, I retained what you said about it and I immediately went to the specs to check that.
Are then any other settings I should make? Perhaps in the Bios? I saw an immense list of settings for the cpu that I didn’t touch, but I think QuickSync was not one of them.
There’s a lot of info here: Plex in FreeNAS jail and vaapi Intel hardware acceleration support as some users have different setups so a few steps might be different.
I’ll DM you and see if I can help, this way we also keep this on topic.
Glad you could upgrade! 
Thank you. Plex needs a good road to walk, it’s definitely not an off-road 
But I’m happy now.
Plex strikes again!
At 2 a.m. I was getting this:
coretemp2: critical temperature detected, suggest system shutdown
coretemp4: critical temperature detected, suggest system shutdown
coretemp4: critical temperature detected, suggest system shutdown
coretemp2: critical temperature detected, suggest system shutdown
coretemp0: critical temperature detected, suggest system shutdown
coretemp2: critical temperature detected, suggest system shutdown
coretemp4: critical temperature detected, suggest system shutdown
coretemp4: critical temperature detected, suggest system shutdown
I looked in the logs and there was Plex performing the scheduled jobs for a few minutes.
The only way to overcome this was speeding-up the fans manually; but this is 24/7 whereas the jobs only last for a few minutes. Even the fan PWM temperature mechanism cannot cope with it if I don’t speed-up the fans. During this time, my FreeNAS GUI is very sluggish, indicating there’s only a little cpu power available.
If you remember, my new cpu is a Xeon E3-1286 v3 at 3.7GHz 8 cores, so a lot of power, how much more does Plex need? I can’t believe that Plex is so ill behaved to its fellow applications. Why don’t you just throttle it? Checking the low priority as I did is not enough. My scheduled tasks last for a couple of minutes. I wouldn’t mind if it lasted for half an hour and wouldn’t do this.
EDIT: I also have this on the Supermicro motherboard log:
| 29 | 2019/03/15 02:05:46 | CPU Temp | Temperature | Upper Critical - Going High - Assertion |
|---|---|---|---|---|
| 30 | 2019/03/15 02:05:47 | CPU Temp | Temperature | Upper Non-Recoverable - Going High - Assertion |
| 31 | 2019/03/15 02:05:50 | CPU Temp | Temperature | Upper Non-Recoverable - Going High - De-assertion |
| 32 | 2019/03/15 02:05:50 | CPU Temp | Temperature | Upper Critical - Going High - De-assertion |
Mea culpa, I’m sorry.
When I bought the server, the seller assured me that he had placed thermal paste on the cpu and replace the cooler. So, against my habit, I really didn’t check.
And I should have checked it before posting. Believe it or not, the cooler was just resting on the cpu, it wasn’t locked, he forgot to turn the vices.
After this, a scheduled job, with the fan in standard speed, doesn’t go above 67 Celsius whereas it was touching the 100 C yesterday.
I should know better than this, I overlooked it, I was lazy.
Mea culpa done.
1 Like
