My red5 CPU load is also fine as long as I don't record something. Thanks, Sebastian On 16 Mar 2014 19:38, "Maxim Solodovnik" <solomax...@gmail.com> wrote:
> trunk is building red5 using maven already > I'll review the code and merge compilation from the trunk. > > red5 was not updated in 3.0.x branch since video calls were broken (still > broken in trunk, will check the release) > > I have not monitored server CPU, but it seems to be ~1% on my machine > > Will double check and provide detailed answers to all of your questions > later today :) > > > On Sun, Mar 16, 2014 at 12:53 PM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > > > Btw: We could also consider downloading red5 server/client from Jenkins: > > > > > https://builds.apache.org/view/M-R/view/OpenMeetings/job/Red5-server/lastSuccessfulBuild/artifact/target/red5-server-1.0.2-M1-server.zip > > > > Although integrating Git and Maven build into ANT is also possible. > > > > What is the preference ? > > > > Sebastian > > > > > > 2014-03-16 18:51 GMT+13:00 seba.wag...@gmail.com <seba.wag...@gmail.com > >: > > > > > http://svn.apache.org/r1577984 does fix to do a Git checkout using > the > > > latest code from their repository and for the client and server. > > > The folder structure is slightly different, needs some further > > adjustments. > > > Also I think some of the patches (Tomcat7 patch) is no more required as > > > the latest red5 is already using Tomcat 7. > > > > > > I have created a ticket to capture the progress: > > > https://issues.apache.org/jira/browse/OPENMEETINGS-950 > > > It will require some more work and review before this piece of work is > > > ready to be merged back to any of the other branches. > > > > > > However I think it might be useful for our CPU issues and moving > forward. > > > Getting rid of the Tomcat7 patches and SVN-kit checkout stuff seems to > > make > > > our life also a little bit easier. > > > > > > Sebastian > > > > > > > > > 2014-03-16 17:19 GMT+13:00 seba.wag...@gmail.com < > seba.wag...@gmail.com > > >: > > > > > > I think there is also a need to do it because partially some ressources > > >> are no more available in the SVN repository: > > >> http://red5.googlecode.com/svn/java/client/readme.txt > > >> > > >> > > >> 2014-03-16 15:25 GMT+13:00 seba.wag...@gmail.com < > seba.wag...@gmail.com > > >: > > >> > > >> I also tried updating to the latest release of Red5 (1.0.2 seems to be > > >>> just released). > > >>> I was more or less successful. > > >>> > > >>> When using red5 in its latest version the CPU usage when doing a > screen > > >>> sharing of the red5 server side process is a lot less. > > >>> > > >>> I can see that there are a couple of issues updating to the latest > red5 > > >>> versions. However letting them too much out of sync was always > > difficult in > > >>> the past as there are regularly changes that you need to duplicate in > > the > > >>> OpenMeetings API/Configuration files et cetera. And of course > > regression > > >>> testing is a pain. > > >>> However we rely on the improvements of the red5 server API. > > >>> > > >>> What is the current status of the red5 version? Our version r4393 is > > >>> from 07/2012 (https://code.google.com/p/red5/source/detail?r=4393) > :) > > >>> We should make a move I think. There seems to be maybe a good point > now > > >>> when there is a new stable release to review a migration to the > latest > > >>> version. > > >>> > > >>> What do you think? > > >>> What are the current show stoppers from upgrading to the latest red5 > > >>> version? > > >>> I can see a couple of issues when upgrading, but it seems there is no > > >>> major incompatibility between OpenMeetings and later Red5 versions. > > Spring > > >>> is now 4.0 in red5. And some minor changes in the red5-web.xml. > > >>> And it seems like the .upload servlet is not correctly initialized. > > >>> I can share my upgraded OpenMeetings instance if anybody is > interested. > > >>> > > >>> Sebastian > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> 2014-03-16 14:28 GMT+13:00 seba.wag...@gmail.com < > > seba.wag...@gmail.com> > > >>> : > > >>> > > >>> Regarding the Red5 CPU usage: I did a couple of tests. It does not > seem > > >>>> to be like previously a writer problem (writer too slow to write > > packets to > > >>>> disk). Even if I comment out the stream listeners so that nothing > > will be > > >>>> written to disk the CPU usage jumps to 100% whenever I start > > recording. > > >>>> I can also see lots of statements similar to this in the log output: > > >>>> [INFO] [NioProcessor-4] org.red5.server.stream.codec.ScreenVideo - > > >>>> Allocating memory for 748 compressed blocks. > > >>>> [INFO] [NioProcessor-4] org.red5.server.stream.codec.ScreenVideo - > > >>>> Allocating memory for 1305 compressed blocks. > > >>>> > > >>>> I have not seen this kind of logging output in past versions of > red5. > > >>>> > > >>>> Sebastian > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> 2014-03-16 12:44 GMT+13:00 seba.wag...@gmail.com < > > seba.wag...@gmail.com > > >>>> >: > > >>>> > > >>>> Hi, > > >>>>> > > >>>>> there is now a FPS per second changer. How does that incorporate > with > > >>>>> the recordings produced? Is the audio and the video in sync no > > matter what > > >>>>> FPS I choose? > > >>>>> > > >>>>> Did anybody monitor the red5 server process CPU while doing a > > >>>>> screen-sharing recording? I can still see the CPU jump to 100% of > the > > >>>>> server process if I start a recording. > > >>>>> > > >>>>> It would be really good to have a demo server instead of doing this > > >>>>> local verification. > > >>>>> > > >>>>> Thanks, > > >>>>> Sebastian > > >>>>> -- > > >>>>> Sebastian Wagner > > >>>>> https://twitter.com/#!/dead_lock > > >>>>> http://www.webbase-design.de > > >>>>> http://www.wagner-sebastian.com > > >>>>> seba.wag...@gmail.com > > >>>>> > > >>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Sebastian Wagner > > >>>> https://twitter.com/#!/dead_lock > > >>>> http://www.webbase-design.de > > >>>> http://www.wagner-sebastian.com > > >>>> seba.wag...@gmail.com > > >>>> > > >>> > > >>> > > >>> > > >>> -- > > >>> Sebastian Wagner > > >>> https://twitter.com/#!/dead_lock > > >>> http://www.webbase-design.de > > >>> http://www.wagner-sebastian.com > > >>> seba.wag...@gmail.com > > >>> > > >> > > >> > > >> > > >> -- > > >> Sebastian Wagner > > >> https://twitter.com/#!/dead_lock > > >> http://www.webbase-design.de > > >> http://www.wagner-sebastian.com > > >> seba.wag...@gmail.com > > >> > > > > > > > > > > > > -- > > > Sebastian Wagner > > > https://twitter.com/#!/dead_lock > > > http://www.webbase-design.de > > > http://www.wagner-sebastian.com > > > seba.wag...@gmail.com > > > > > > > > > > > -- > > Sebastian Wagner > > https://twitter.com/#!/dead_lock > > http://www.webbase-design.de > > http://www.wagner-sebastian.com > > seba.wag...@gmail.com > > > > > > -- > WBR > Maxim aka solomax >
