[osg-users] SingleThreaded leading to whole application just running on one core

Robert Osfield robert.osfield at gmail.com
Fri Sep 23 02:00:40 PDT 2016

Hi Chris,

On 23 September 2016 at 09:19, Christoph Weiss <weiss at wsoptics.de> wrote:
> This actually has a very bad side effect that I only noticed now.  Since it
> explicitly sets the affinity to core zero, any other application that does
> so will share its CPU entirely with it.  In particular if you start a
> SingleThread OSG application twice, it will share the core and have degraded
> performance.

The OSG primary focus and expected user base is real-time
visualization with such applications you won't run multiple
applications at the same time and you'll be using the OSG's native
windowing, multi-threading, database paging etc. Out of the box the
OSG tries to work as well as it can for this usage model.

The OSG isn't just about real-time visualization, even if this is it's
primary focus, it does support other usage models as well, but out of
the box I wouldn't expect all the design decisions based on the above
focus to work as well, what is important is that one can adapt the OSG
to work well for these other usage models even if out of the box it
doesn't do it perfectly.

In the case of Qt usage, perhaps osgQt could provide sublcasses from
Viewer/CompositeViewer to help adapt the OSG to work better for a
typical Qt users requirements.


More information about the osg-users mailing list