And as Jochen well said, unfortunately this doesn't solve the problems of
current projects...
Any chances of a service pack to fix such issue on 2003 or it's a big
change and will only be available on whidbey?
Sure. I think I can give you a workaround for it in everett.
From your code
#include <time.h>
#include <stdio.h>
/*******Note the pragma unmanaged *******/
#pragma unmanaged
class MyTest1
{
private:
int s_i;
virtual void Test1(int i)
{
s_i += i;
}
public:
void MakeTest()
{
clock_t start, finish;
double duration;
start = clock();
for(int i = 0; i< 10000000; i++)
{
Test1(i);
}
//EndTimeMeasure();
finish = clock();
duration = (double)(finish - start) / (CLOCKS_PER_SEC);
printf( "%2.1f seconds\n", duration );
}
};
int main()
{
MyTest1 obj;
obj.MakeTest();
}
When you compiled your native class with /clr, it causes what is called
double thunking. A call is made from a managed call site to a mangaged
function definition via a native vtable.
Yes, that is right. The vtable is native in this case so there is
performance penalty when you make a transition from managed - native and
native - managed. When I applied #pragma unmanaged over the function
definition, I reduce the thunking from native to managed and thus saved the
performance penalty. On my everett compiler this code took .4 seconds vs
13.5 seconds if I dont use #pragma unmanaged.
Please let me know if this fixes your problem.
Thanks, Kapil
