B
bartj1
Hi,
I did a benchmark comparison of a National Instruments Active-x "Strip
Chart" control in both Vb5 and vb.net(2005). The code is identical:
For I = 1 to 10000
ARR(1,0) = J
AxCWGraph1.ChartY(arr)
j = J + 1
If j > 10 then j = 0
Next
It takes .8 seconds for a VB5 exe to run and 3 seconds for a .net exe
to run(same machine).
I realize that a .net component would be the better way to go instead
of using active-x in .net, but why the HUGE speed diff?
Thanks,
Bart
I did a benchmark comparison of a National Instruments Active-x "Strip
Chart" control in both Vb5 and vb.net(2005). The code is identical:
For I = 1 to 10000
ARR(1,0) = J
AxCWGraph1.ChartY(arr)
j = J + 1
If j > 10 then j = 0
Next
It takes .8 seconds for a VB5 exe to run and 3 seconds for a .net exe
to run(same machine).
I realize that a .net component would be the better way to go instead
of using active-x in .net, but why the HUGE speed diff?
Thanks,
Bart