Nonecure,
Have you noticed any difference in performance? Is the 2010 sp1 exe running any faster? It is difficult to tell manually if you have devices installed that the LabVIEW code has to wait on and there aren't any major LabVIEW sections of your code. If you don't have much code you can put it in this simple benchmark vi example and see how that goes. Also adding Veristand to LabVIEW will give you benchmarking capibilities.
From the article that bp4807 pointed out, "one of the primary focuses for the 2010 release of LabVIEW was optimizations inside the compiler to speed VI execution time."
Optimizations come with certain tradeoffs. Check out the Compiler Optimizations wiki link. I would especially pay attention to the Common Themes section. Items like "Fewer jumps" is going to make your code run faster, but actually end up increasing the files size of the executable.
Another possible reason is that the code in LabVIEW 2n010 adds additional functionality ad backwards compatibility. When you compile in 2010 if you have VIs from 2009 that transferred over, the 2010 version will be compiled using the 2010 VIs and which may have different block diagrams.
Regards,
Michael M
NI Americas | AE
NI.com/support | 1-866-275-6964
