Harpertown is 59% faster than Barcelona
......Or.. Barcelona is 10% faster clock for clock....
You can pick the headline...
This from the ever reliable Inquirer
http://www.chipzilla.com/?article=41868
3.2 ghz 1600 mhz fsb Harpertown (4 cores, 2 x 6 megs cache)
=> 102 GFLOPS peak (Linpack)
=> 80 GFLOPS sustained (Linpack)
2.0 ghz Barcelona
=> 64 GFLOPS peak (Linpack)
=> 55 GFLOPS sustained (Linpack)
Notes:
In Absolute terms
Harpertown is 102/64 => 1.59375 times as fast (peak)
Harpertown is 80/55 => 1.4545 times as fast (sustained)
On a clock for clock basis:
Barcelona is (3.2/2.0) / 1.59375 = 1.00392 times as fast peak (a draw given MOE)
Barcelona is (3.2/2.0) / 1.4545 = 1.1000 times as fast sustained
Other notes:
The Inquirer discribed the code being run on Barcelona as "with the most optimised new PGI compilers for the platforms"
The Inquirer discribed the code being run on the Intel machine as "not yet fully optimised"
The Intel was runnning of FB Dimms, which are not noted for great performance
Editorial Comments:
Lindpack is highly I/O intensive
Lindpack correlates poorly to the real world.
......Or.. Barcelona is 10% faster clock for clock....
You can pick the headline...
This from the ever reliable Inquirer
http://www.chipzilla.com/?article=41868
3.2 ghz 1600 mhz fsb Harpertown (4 cores, 2 x 6 megs cache)
=> 102 GFLOPS peak (Linpack)
=> 80 GFLOPS sustained (Linpack)
2.0 ghz Barcelona
=> 64 GFLOPS peak (Linpack)
=> 55 GFLOPS sustained (Linpack)
Notes:
In Absolute terms
Harpertown is 102/64 => 1.59375 times as fast (peak)
Harpertown is 80/55 => 1.4545 times as fast (sustained)
On a clock for clock basis:
Barcelona is (3.2/2.0) / 1.59375 = 1.00392 times as fast peak (a draw given MOE)
Barcelona is (3.2/2.0) / 1.4545 = 1.1000 times as fast sustained
Other notes:
The Inquirer discribed the code being run on Barcelona as "with the most optimised new PGI compilers for the platforms"
The Inquirer discribed the code being run on the Intel machine as "not yet fully optimised"
The Intel was runnning of FB Dimms, which are not noted for great performance
Editorial Comments:
Lindpack is highly I/O intensive
Lindpack correlates poorly to the real world.