Re: [reSIProcate-users] High CPU consumption by reSIProcate 1.8.5

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Looks like this problem was caused by a Fifo flush call in the TCP Transports, that ended up signalling the select interrupter with every process loop, so it would spin tight.  I've committed a fix to main line and the 1.8 branch - it will end up in 1.8.6 when it is created.

Regards,

Scott

On Wed, Dec 5, 2012 at 5:51 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:

Interesting.  Just did some testing and see one core using up to 13% all the time.  I think I found where the problem is.  I should have a fix tomorrow sometime.

Regards,

Scott

On Wed, Dec 5, 2012 at 5:14 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi,

 

                We have upgraded from reSIProcate  version 1.7.1 to version 1.8.5.

 

                But in version 1.8.5 we can observe a bad behaviour that wasn´t present in 1.7.1:  

There is a high CPU consumption (full use of one CPU core) by the thread running resip::InterruptableStackThread::thread()

 

We have tested in Windows 7 Professional – SP1, building with Visual Studio 2010.

 

This can be easily spotted by building reSIProcate_10_0.sln and running the test app basicClient.

 

Regards.

Julio Cabezas

 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/