Hello Brian,

 

The 95-110% in top means 95% of one processor to 100% of one processor
plus 10% of another. If it said 2400% it would be using all of the 24
cores in the worker. I like htop better than top as it has a usage bar
for each core and is easier to use (IMO). Like others have said not all
codecs will use all the threads when encoding, but most will if
configured properly. Or if left alone you could have 24 concurrent
processes going and they would all be just as fast as the one which is
good if there are a lot of classes scheduled around the same time.

 

All the best,

 

Luke

 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Brian
Bolt
Sent: Thursday, December 30, 2010 10:55 PM
To: Matterhorn Users
Subject: [Matterhorn-users] Ramping up production environment

 

I have a distributed install running 1.0.1.  The Admin and Engage
servers each have 16 cores (Intel).  The Worker server has 24 cores
(AMD).  My first one minute capture took about five minutes to process.
My second capture is an hour long, and at 1 hour into processing it is
currently encoding the presentation (screen) for preview.  

 

I expected that the Worker server would endure the greatest processing
load, and 'top' shows that ffmpeg is using 95 - 110% cpu.  However, when
I run mpstat -P ALL, all processors are greater than 95% idle.  Based on
what I saw in my VM test environment, I anticipated that a 1 hour
capture would take well under 15 minutes to process.

 

On another note, the amount of space consumed is very large, 345 MB for
the one minute capture an 15.6 GB for the one hour capture.  Note that I
don't yet have the workflow yet configured for streaming, so I
anticipate that these numbers would be even larger if streaming were in
the mix.

 

[r...@server matterhorn]# du -h --max-depth=1

25M     ./streams

8.8G    ./files

6.5G    ./workspace

68K     ./server1

2.5K    ./inbox

78K     ./searchindex

22M     ./downloads

16G     .

 

Thoughts and ideas are greatly appreciated.  

 

Thanks,

Brian

_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users

Reply via email to