Tony Peden writes: > > What property-related methods show up > > near the top in the profiling? > > SGPropertyNode::getDoubleValue() > > This makes perfect sense, because it's called in place of > FGState::GetParameter which used to be the big hitter.
I had been thinking about eliminating tying to pointers, but in my own tests, I have had very little luck speeding up tying to object methods, so maybe tying to member variable pointers is a reasonable alternative (it also avoids all the template madness). I can optimize that a bit as well. When you use this approach, instead of node->tie(SGRawValuemethods(this, Foo::getBar, Foo::setBar)); you would do node->tie(SGRawValuePointer(&bar)); This works, of course, only if your getters and setters don't massage or clamp the values at all. There are some easy optimizations I can perform to make tied pointers as fast as internal values, if they turn out to be helpful. All the best, DAvid -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
