Jump to content

transcoding problem


Muad

Recommended Posts

i have a intel core i7 930 cpu and 12 gig with ram, 
I am trying too transcode mulitple streames too diffrent users.
But it seems that my system overloads and  crashes when i do that, i have set the cpu count too 4 too over come the system crashes. but still the users complains that what they are watching is laggy,
Is my hardware too small too handle 2 - 4 transcoding at the same time ?  
 

transcode_log.txt

server_log.txt

Link to comment
Share on other sites

  • 3 weeks later...

It should be able to do it. check your load average (via top or uptime)

 

You'll see load average: 0.78, 0.78, 0.78

That means number of process running / number that want to run for 1, 5 and 15 minutes.

 

If your under high load (anything over maybe a 4 or 5) you may be at your limit.

 

There are a few things you might try. Run the server under a Jail as opposed to a VM

Set compiler options in your make.conf and rebuild the port such as:

 

CPUTYPE?=corei7

 

I think thats right you'll have to check, I have AMD hardware, also be careful with that and don't set -O flags and the native flag is supposed to be bad to set also. thats about all you can do tho and any gains will be pretty small.

 

Edit: also there is htop or slmon that gives you a nice cpu bar graph.

Edit2: ZFS compression modes can eat up CPU also. lz4 (the default) should be ok but its not needed on media because its already compressed.

Edited by jdemby
Link to comment
Share on other sites

  • 2 weeks later...

load averages: 6.93, 3.40, 1.61
that is from one transcoding thread, having more than 2 threads running on the server at once is not working.

I see the ffmpeg has -0:s flag set... 
cant find a way too tweak the flags ffmpeg is using? 

maybe time too upgrade too a xenox server if i need more threads too transcode videos, but fracking frack the xenox cpu is expensive

hw.model: Intel® Core i7 CPU 930 @ 2.80GHz
hw.machine: amd64
hw.ncpu: 8

 

Link to comment
Share on other sites

I would suggest going back to automatic thread count because ffmpeg is usually pretty good at managing it on it's own.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...