[...] Secondly, the serial C++ implementation is much faster than I’d expect when compared to the C# native C++. 4x speedup just seems odd. This suggests that my C# code could be more efficient but this might be at the expense of readability. The C++ code uses macros to modify the BodyNative struct’s data directly whereas the C# code does so through via methods on the Body class. If these method calls aren’t placed inline then this could well be the cause (see previous post on C# and inline methods). [...]

[...] after my performance investigation the other day, got me wondering again. Is there performance really going to be bad? Surely the compiler could [...]

[...] C# Inline Methods and Optimization Questions on application domains, application pools and unhandled exceptions Did you know… How to [...]

Thanks!

http://blogs.msdn.com/saraford/archive/2008/08/13/did-you-know-how-to-optimize-your-code-for-a-build-290.aspx

Regards,

I guess ill thought out (Manager trying to code) concern when I wrote the class was around memcpy overhead. Thinking about it further the Vector is only three doubles so it should be a struct. It “behaves” like an int so it should really be a struct. Time to rewrite it.

In general though it’s interesting to figure out what the compiler(s) are doing under the hood. It might even make me a better programmer one day… maybe.

Thanks

Thanks for pointing this out! It’s a really good post and explains the tradeoffs involved in when to inline and when not to.

Seems like simple property accessors will almost always be inlined as the inline code (one instruction) is less than the call (five instructions) even with a miltiplier of one:

If InlineSize <= NonInlineSize * Multiplier do the inlining

Thanks

http://blogs.msdn.com/vancem/archive/2008/08/19/to-inline-or-not-to-inline-that-is-the-question.aspx