Allen Bierbaum wrote:
> [...]
>> I've profiled our app and 10% of the time in OSG-dlls is spent in 
>> GetAspect(). That's quite a bit and therefore I'm happy to see 
>> c-pointers being introduced in C++. Hopefully, it will also reduce 
>> compile times & code size. (No more copy-ctoring of FCPtrs everywhere).
> 
> Did your profiling separate application level use from internal use? 

No. That would require call-graph profiling (as opposed to an 
event-based), which takes ages to run, so I haven't done that just to 
track this.

> I 
> agree that the current ptr's have too much overhead to use in 
> performance critical sections of the internal code, but my assumption 
> was/is that if an application (whether C++ or python based) uses 
> aspect-safe RefPtr's that this overhead is minimal compared to the time 
> spent on rendering, traversal, and all other things internal.
 >
> I don't have any numbers to back this up though so I could be wrong. :)

The thing is that we do a fair bit of OpenSG manipulation in our 
"main-loop", it's just not chaning a few matrices and calling render(). 
So it could mean more for us.

But I haven't got numbers for that either.. ;)

Another benefit for us is that the reduction of template-code will lead 
to faster compile times.

Cheers,
/Marcus


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to