09-22-2010, 03:52 PM
well, also as everybody knows - "Intel sucks" ;)
Actually Igor, there can be a lot of optimization in any program. This can be done either by the author, or the compiler can do the work automatically. I assume that the M$ .NET $hit just has some array optimized libraries, which the compiler selects to be used in your case.
It is better to use some really real example, and then to compare and decide which one does it faster. Also I am suspicious about some file read/write optimizations that M$ is doing - so try to avoid reading/writing small files in the test.
Also very strange on my computer - the time of the VB.NET EXE is the same as yours, but the Intel Fortran's EXE - differs. Why my times are less on a 64 bit OS - are you using Pentium IV? (don't compare anything on this CPU - it is a real crap - upgrade to "Core" at least).
You can also check Portland's (PGI) Fortran - there should be some reason to sell and update so frequent their compiler.
Actually Igor, there can be a lot of optimization in any program. This can be done either by the author, or the compiler can do the work automatically. I assume that the M$ .NET $hit just has some array optimized libraries, which the compiler selects to be used in your case.
It is better to use some really real example, and then to compare and decide which one does it faster. Also I am suspicious about some file read/write optimizations that M$ is doing - so try to avoid reading/writing small files in the test.
Also very strange on my computer - the time of the VB.NET EXE is the same as yours, but the Intel Fortran's EXE - differs. Why my times are less on a 64 bit OS - are you using Pentium IV? (don't compare anything on this CPU - it is a real crap - upgrade to "Core" at least).
You can also check Portland's (PGI) Fortran - there should be some reason to sell and update so frequent their compiler.