Icecast - Feb 2005 - Re: Severe problem with Icecast2 and streamTranscoder

Geoff Shang wrote:
> You *definitely* have enough CPU?  Transcodes can be expensive.
Yeah, there's a lot of spare CPU power and memory.  The icecast server 
takes 0,0% CPU and each streamTranscoder instance only takes 0,0-0,3%. 
This is a dedicated Icecast server with 1GHz PIII and 512 MB RAM.
> Also, have you looked in the Icecast error log?
Yep.  Nothing there.  The only clue I've found is the recurring "Read
-3
ret from ov_read" message in the streamTranscoder debug logs (see my 
earlier link to the sT bug report).  Not that I can make anything out of 
that.

It seems that other people are having very similar-sounding problems:
http://www.oddsock.org/openbb/read.php?TID=1685

-- 
Antti N?yh?                 "Ich bin der Zorn Gottes;
http://www.sairwas.org/         wer sonst ist mit mir?"

On Wed, 09 Feb 2005 19:12:30 +0200, Antti N?yh? <sairwas@sairwas.org>
wrote:
> Geoff Shang wrote:
> 
> > You *definitely* have enough CPU?  Transcodes can be expensive.
> 
> Yeah, there's a lot of spare CPU power and memory.  The icecast server
> takes 0,0% CPU and each streamTranscoder instance only takes 0,0-0,3%.
> This is a dedicated Icecast server with 1GHz PIII and 512 MB RAM.
That's very, very unlikely. 'streamTranscoder' is normally used to
transcode streams (as far as I know, it's not possible to use it
without that), and even _decoding_ your incoming vorbis stream (I
assume it's vorbis, from the error message you give from
streamTranscoder below) is going to take much, much more than 0.3%
cpu. Encoding will take a lot of what's left...

This still sounds more likely to be cpu starvation than anything else,
and if whatever tool you're using to get cpu usage is telling you that
streamTranscoder is using that little cpu... well, I wouldn't trust it
at all (note that most of the common cpu-usage measuring apps have
sampling errors that sometimes make them misread really, really
badly).

Mike