I've been doing extensive benchmarks on my Athlon 64 3400+ doing Verilog
simulation, Xilinx FPGA place and routes and GCC builds. If there isn't
any IO, i.e. a verilog simulation that doesn't save a .trn file,the Athlon
64 is nearly twice as fast as by 2.66GHz Xeon (1.95 to be exact). When I
do a verilog simulation that saves a large .trn file (340 Mbyte) the
Athlon 64 is still 40% faster than the Xeon, and remember this is a laptop
with a 4400 RPM disk vs a server with a 7200RPM disk. Doing a big GCC make
the Athlon 64 is 77% faster than the Xeon. Sites like Tom's and Anand
focus mostly on games and multimedia applications. The P4 can hold it's
own on games because those make very heavy use of the multimedia
instructions. Most applications that a developer will run don't make any
use of the multimedia instructions. The results that I've seen are typical
of both hardware and software developer performance.
I've had the laptop for a little while now and I've got it running
solidly. I had to do a couple of things to get everything to work, here is
a summary
Compaq R3000z, Athlon 64 3400+, 1G DDR, 60G drive, 1680x1050 screen,
Nvidia graphics, Broadcom 54G wireless, XP Pro (just in case I ever need
Windows for anything, XP home is $49 cheaper but if I have to own a copy
of Windows I rather it's one that works), and a worthless winmodem. ($1525
from
http://www.hpshopping.com ).
Fedora Core 2, 32 bit version (necessary because I use Win4Lin and
ndiswrapper). The 64 bit version works fine but I didn't see any important
performance differences so I'm running 32 bit because of the
aforementioned Win4Lin requirement.
2.6.8.1 kernel. I built this myself with the Win4Lin patches and I
targeted it to the K7 (Athlon). I had to disable register parameters
because they caused Win4Lin to core dump. I also disabled preemptive
schedualing (at NeTraverse's suggestion). I turned on the K8
power management and the userspace clock speed control (works great, you
can switch the clock speed from 800MHz upto 2.2GHz with a simple echo to
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
for example,
echo 2200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Installed ndiswrapper and the Windows XP driver for the Broadcom 54G
802.11B/G card. Works perfectly. Very easy to setup.
Installed the Nvidia driver. Works fine once I got the kernel issues
ironed out.
Had to hack the xorg.conf file to make the 1680x1050 screen work, do a
Google search for 1680x1050 and Linux and you'll find the instructions on
what to do (the webpage poster has a Dell Centrino with the same screen).
The only thing that will never work is the winmodem. I've ordered a USB to
serial port adapter form Keyspan (they actively support Linux according to
both the kernel documentation and their website). I'll use an external
modem when I travel.