[osg-users] Processor Affinity and forked processes

[Robert Osfield]

Hi Kristofer,

I merged what were supposed to be "fixes" to the OpenThreads from a user
submissions between OSG-3.2 and 3.4.  The change in behaviour might stem
from this, try reverting these changes and see what happens.

Robert.

On 16 November 2015 at 11:09, Kristofer Tingdahl <
kristofer.tingdahl at dgbes.com> wrote:

> Hi,
>
> we just found and solved the most weird bug that was associated with our
> upgrade from OSG 3.2 to OSG 3.4 .
>
> Our problem was that our batch programs (i.e. number-crunchers) would only
> run single threaded when launched from our application, but multi-threaded
> when launched on the command line.
>
> After 10 hours debugging, we found out that OSG 3.4 sets the CPU affinity
> from osgViewer::ViewerBase::startThreading(). When the process forks, this
> setting is inherited by the new process, and hence limits the new process
> to only run on one physical CPU.
>
> Our solution to this was to let the new processes unset the affinity mask,
> but I wish to make the community aware of this unwanted effect of OSG 3.4
>
> Best regards,
>
>
> Kristofer Tingdahl
> --
> *Dr. Kristofer Tingdahl**Chief Executive Officer*
> *______________________________*
>
> *dGB Earth Sciences*Phone:+31 53 4315155Skype:dgbtingdahlE-mail:
> kristofer.tingdahl at dgbes.comInternet:dgbes.com & opendtect.org
> *______________________________*
>
>
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20151123/241ac2e0/attachment-0003.htm>