Hi Uma,

Changing the OpenThreads backend will not change the performance you
see, it's just changing who sets up the threading.

With performance testing it only makes sense to do it with a release
build as debug build increases the CPU overhead massively and totally
distorts the framerates and crucially the relative balance for what
takes longest in the frame.  The later is important to optimization
work as you want to spend you time most effectively by fixing the
biggest bottlenecks,

As for how to make things faster, you don't provide any information
whatsoever about what your models are, the size of them, the hardware
you are working on, what the relative costs of the different
traversals.  There isn't anything we can do to advise you on such an
open ended question.

For instance, a question for you, I have a piece of string, could you
please tell me how long it?  Can you answer?

Robert.

On 18 October 2016 at 09:09, Uma Devi Selvaraj <umaselvam1...@gmail.com> wrote:
> Hi all,
>
>         Regarding openthreads access violation issue,today I tried to build 
> osg without(BUILD_OPENTHREADS_WITH_QT) cmake options. And I tired to use 
> those exe and dll files to run my example code. I am able to render 3D model 
> Successfully in both debug and release mode, the problem is it is taking too 
> mush of time to render. Is there any to way to render the model quickly.
>  And I just want to know use of BUILD_OPENTHREADS_WITH_QT option.? Will it 
> create any issue if I build OSG without this option.?
>
> ...
>
> Thank you!
>
> Cheers,
> Uma
>
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=69050#69050
>
>
>
>
>
> _______________________________________________
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to