From Christian Ehrlicher, "during profiling my program I found out that there's a lot of memory (de)allocation going on in OverlayNode::cut().
From Christian Ehrlicher, "during profiling my program I found out that there's a lot of memory
(de)allocation going on in OverlayNode::cut().

So instead creating inner-loop variables 'distances' and 'newVertices'
every time, I moved the creation out of the loop and just do a clear() +
reserve() inside the loop. This allows std::vector<> to reuse the old
memory instead allocating new when the new size <= oldsize."


ntoand/osg,ghub/osg,ghub/osg,stmh/osg,omega-hub/osg,XiaoCC/osg,omega-hub/osg,artoolkit/osg,omega-hub/osg,koshman86/osg,ghub/osg,stmh/osg,ntoand/osg,stmh/osg,XiaoCC/osg,omega-hub/osg,stmh/osg,XiaoCC/osg,koshman86/osg,XiaoCC/osg,XiaoCC/osg,ntoand/osg,koshman86/osg,artoolkit/osg,stmh/osg,ntoand/osg,ghub/osg,artoolkit/osg,koshman86/osg,artoolkit/osg