We're battling with a very odd problem. We're brining on about one hundred new rtmp streams, encoding from digital rapids. This is what we see so far.
We are seeing multiple issues but i shall highlight a few.
When pushing about 30 2mbps streams to a wowza on Ubuntu/Centos we see massive CPU loading when using a 'live' type, but not 'default'. We removed the http segmenters stuff from the Application.xml to eliminate that.
We dont see the issue from FMLE, only digital rapids and exaggerated when using b-frames. We see the problem much worse from the 64 bit version of DR Stream.
I am thinking its to do with video/audio sync problems and have added the <sortPackets> lines to the Application.xml - doesn't help. We have tuned and fiddled and tried most things, different versions of Java etc
****It doesn't happen on another machine running windows 7****
Dodgy hardware? But why invoked when going from type 'default' to type 'live'
Please help its driving us mad.