Hi Maurilio, > Viktor, > > for real code, doing I/O on a network share, the difference could be lower, > though.
Yes, of course speedtst is not the one-and-only ultimate bench, though it still shows big difference in a lot of important places, f.e. a table upgrade or reindexing on server. Double the speed is big difference. BTW I can feel much smaller difference even with procedural CUI app, and this is pbly much noticeable in OOP and/or GUI apps where much more .prg code is pumped trough the HVM/CPU. Fast execution can most probably make these apps to behave "snappier" and thus user experience better. It's IMO also important to actually exploit the possibilities of hardware and not waste the cycles / wattage / users' time, nerves / etc. BTW, it'd be interesting exercise to see how faster gcc/mingw gets with lower optimization levels and how execution speed drops. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
