[Smtk-developers] More performance info

[Robert Michael O'Bara]

Hey Dave,

Sounds like the only way to improve the speed is to reduce the number of tessellants being produce (especially since it looks like we are over tessellating in some parts.

Bob 

Sent from my iPad

> On Dec 23, 2014, at 7:08 PM, David Thompson <david.thompson at kitware.com> wrote:
> 
> Hi Bob (et al.),
> 
> The vast majority of the time spent after the STEP import (i.e, obtaining the tessellation) is in OpenCascade (75-85%). CGM and SMTK spend the remainder translating the topology and evaluating "measure()" on each CGM face in order to determine a per-face chord error limit. The "measure()" call accounts for 10% of the post-import time. So if we can get by without calling it, it would be nice. However, in terms of real speedups, it does not look like much is available outside of improvements to OpenCascade.
> 
>    David