Maurilio:
I've got these results
PIV 2.4GHz UNI -- PIV 3.6GHz HT SMP
CPU INT 2001.95 2863.38
CPU FLOAT 91.49 217.92
>MEMORY 4481.71 5213.02
And your speedtst.prg results in UNI ? Are very different of SMP ?
so, pc speed seems ok, but, I've noticed one thing, when I run speedtst
on the UNI kernel I see that the single CPU is maxed out (using OS/2
version of task manager, just to give you an idea).
When i run it on the SMP kernel, though, both CPUs keep going up and
down, in spikes, as if there is some call which suspends the program
>for a certain amount of time.
This peculiar behaviour does not happen when I run the speed comparison
tool, so it has to be something inside speedtst and/or harbour runtime
and/or gcc runtime, but I don't understand what!
I saw same behaviour
In AMD Athlon CPU goes 100 % in OS/2 but in Windows XPP SP2 and Linux
Mandriva 2008 too
In Core2Duo:
Windows Vista HP: both CPU alternate 60% / 40%
Windows XPP SP2: both CPU alternate 80% / 20%
OS/2: refuse to install due hardware
Linux Mandriva 2008.1: mainly 5% / 100 % second CPU does everything
At last all seem to be an OS decision
I made "long-runs" adding a 0 to:
#define N_LOOPS 10000000
so is 10x greater. Results are linear, time consumed was 10x
David Macias
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
