okay,

as some may have noticed, i started the thread on performance timers... which is now sorted. But having got it sorted, my time comparisons are a little *bad* as you can see:

okay, first up - test machine:
700mhz Athlon Thunderbird / 288mb PC100 RAM (ie, not slow!)

I'm testing the maths/memory manipulation type things w.r.t. using VB.Net for high performance (okay, i know it aint top-of-the-line) multimedia/graphics work... thus speed is critical.

here are my results:

MATHS FUNCTIONS:
in order: sqrt, sin, arccos, arctan
(times in nanoseconds)

VB6 | VB.Net | VB.Net is...
=======================================
281.8882 | 630.0195 | 123.5% slower
265.1841 | 665.9771 | 151.14% slower
883.1846 | 1041.6985 | 17.95% slower
326.3383 | 927.4561 | 184.2% slower

MEMORY MANIPULATION:
in order: alpha blend test, memory addition
(times in milliseconds)

VB6 | VB.Net | VB.Net is...
======================================
20.7814 | 80.5359 | 287.54% slower
104.9186 | 155.8228 | 48.52% slower

okay, the VB6 code and VB.Net code is pretty much identical (as much as is possible). VB6 code is using the most optimized native compile as possible (for speed). VB.Net is just set to the "release" configuration and run through windows (not with debugger attached)...

Please tell me I'm missing something really obvious with respect to speed-compiling a VB.Net program - these results are awful! IT HAS TO BE MY FAULT!!!

can someone give me good reason to kick myself and make VB.Net run a little bit faster

Jack;