First Round of AMD Athlon 64 Reviews In
wrinkledshirt writes "Here's a bunch of AMD Athlon 64 reviews, courtesy of 8Dimensional." AcesHardware and HardOCP match the Athlon 64 line against the Pentium 4 Extreme Edition. amdmb, FiringSquad, and SharkyExtreme take a closer look at the FX-51. AthlonXP and PCStats have glowing reviews of the chips. Digit-Life compares the new Athlon 64 with Opteron and a Pentium 4. LegitReviews and Overclockers.com.au also both have succinct reviews of the FX-51. Overall the reviews speak very highly of the Athlon 64 and the FX version of the chip, with the only downside being the cost, especially of the FX chip.
Is it possible to have a first round of reviews after an earlier story about Athlon 64 reviews?
fp
Reliable, Great Value Hosting: $7.95/mo 2.4G/120G
Enough! Leave me alone with my abacus...
Um, anyone knows how many bits can an abacus counts to?
Will sys-admin for food
Give it a bit more time. The motherboards can still be tweaked to get more performance out of the system. I think we should wait a bit before really making decisions, and get in a whole load more real world testing too.
Benchmarks are not always entirely, although often can be, illuminating.
The OS is 64 but most of the games/applications are 32 bits ?????
The socket format will be changing soon, and once the upcoming changes happen, things will be much better. You'll then be able to use non-ECC memory, and the motherboards will be less expensive.
Until then, yeah, the FX is freaking fast, but waaaaay overpriced, so don't bother.
A 64-bit address space is probably a good thing once a program is allocating 2GB or more of address space.
Are avalible from SuSE, Gentoo, and Debian!
SO if you are complaining "theres no 64 bit os yet", stop complaining, leave the evil empire behind and see the REAL power of opensource.
Damn! You stole my thunder; I was going to post this benchmark.
I think the biggest con of the FX51 is that soon it will be orphaned because of the 940pin -> 939pin change, which will allow that particular core to use normal DDR400 memory instead of registered ECC DDR400 memory.
SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
None of the above. It was Digital, with the Alpha AXP chips. It runs native 64bit Unix/VMS and 32bit Windows. Also x86 emulation via the !FX emulator.
while it's very likely that this is the case for the reviewing samples (probably rushed out as fast as possible, I can't believe that Intel had plans for the EE all along given that there were 0 leaks) given that this is a paper launch by the time the EE will actually be available to customers I'm sure the MP support will disappear.
-- the cake is a lie
Not quite.
The AMD64 core uses a 40-bit physical memory address space, which is 1 Terabyte. It also uses a 48-bit virtual memory address space, which is 256 Terabytes.
A full 64-bit physical memory address would allow for 16 Exabytes of memory.
SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
The multi-cpu support may or may not be still enabled, but the P4 EE has a different pin count than the XeonMP, so you wouldn't be able to use it in the XeonMP boards anyway.
this is not a problem with an abacus as you can own an original 8 bit abacus and just add 8, 16, 32, or even 64bit upgrade kits. You may need a larger frame to accomadate the beads but you'll have years of growth from your very own abacus.
We've got a couple of Opterons at work, one for 32-bit compatibility testing, and another for the AMD64 port. It's pretty cool to see this in Python on SuSE Linux 8.2 beta:
SuSE Linux 9.0 for AMD64 is supposed to ship next month. Hopefully, it will be a little cheaper than RHEL 3.0 for AMD64, which will be more than twice the price of RHEL 2.1 for x86!I am still blown away that the FX did better then then 3.2 P4.
Proper benchmarks include not using a 64bit beta stupid o/s like windows, a properly optimized linux (suse 64 or gentoo) and applications built for the chip. Openoffice, kde and kde apps, mozilla, some miscellaneous 3d engines running some impresive demos, maybe tenebrae quake. Tenebrae quake is great being that its open source and takes a huge amount of gfx and proc power.
Correction =! != !=
The results? The 64 bit version took nearly HALF THE TIME of the 32 bit version. This is the kind of thing we have to look forward to in some things (MP3s, video encoding, etc).
The Athlon 64 is fast in 32 bit mode, and can beat a P4 many times. But when the 64 bit code comes along, the P4 will be taking one hell of a beating.
PS: Sorry I don't remember which review had this test. I don't have time to go hunting for it right now.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
I've been struggling to find any good 64 bit resources for Linux.
:-)
Basically, I want to know about all the 64 bit versions of major apps and systems, like MySQL, Perl, and so on. I know Perl is in 64 bit, because you can compile it to be, but what about stuff like MySQL, Apache, TomCat...
Post your best 'going up to 64 bits on Linux/FreeBSD/elcheapo UNIX' resources here, and attract some karma
Web Hosting Reviews
Found it! It was Anandtech. Check out the bottom of the 32 bit vs 64 bit page of the review.
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
Organic integrated circuits are produced without using fertilizer or pesticide.
The point about mmap(2) is to let the system (the VM subsystem of the kernel) manage the caching for the userland processes using it, avoiding extra copies to/from buffers in userland and eliminating in several cases the need for custom caching code (processes don't have to worry about data being available in RAM: the kernel automatically takes care of that when needed).
You don't need gobs of memory to do this, but in order to work on large amount of data you need a large address space, which is what 64 bit architectures provide. Of course, the more physical memory you have, the less the kernel has to swap pages in and out, but the main point is not that.
A little example to clarify: in order to keep things simple (instead of needing two intermixed caching systems, one for the VM and one for disk accesses), the Hurd just mmaps the whole partition. This means that the maximum size of a partition has an upper limit given by the size of the addressing space, which is 4GB on 32bit architectures (actually less, since in that address space you have to keep also the code that uses the mmapped data, so it's more like 2GB/3GB). A 64bit architecture comes very handy here, given the current size of hard disks.
Makes ya wonder whether a company such as Powerleap might come out with a CPU adapter to support it. For a long time the Athlon MP series offered the only affordable SMP solution, especially if like me you found a pair of Athlon XPs which worked happily in SMP mode.
http://www.aceshardware.com/read.jsp?id=60000253
has a cooling technology that allowed them to overclock to a 2.8 Ghz Athlon FX. It was pretty impressive stuff, especially how well Age of Mythology did, even against the non-shipping P4 Emergency Edition.
I can't wait until theres 64 bit games for this sort of thing. Of course, the first to be released will be Unreal Tournament. Oh yahh!! I know I'll own at least one of the AMD64 computers within the next year!
I'd love to have a new AMD64 for my application server. There were benchmarks on extreme tech showing a 1.6 Ghz dual opteron beating a 2.8 Ghz quad xeon by gigantic margins (almost double). So when these Athlon 64 processors trickle down to the same clocked Opterons, it should start to shake up the server market even more. Especially given upcoming backing from Sun:
http://www.theinquirer.net/?article=11772
Doesn't anyone realize that the Athlon 64 isn't going to be anything special until they start testing on a 64-bit platform???
hi
Some apps require large blocks of contiguous memory - and with only 2GB of address space available, you can actually run into address space fragmentation problems long before you run out of physical memory. There simply isn't a large enough span of addresses available to map the memory into.
Other things compete for address space too. System DLLs map themselves into various places, leaving too-small gaps between them. Threads reserve 1 MB each, for the stack grow. Some PCI boards (e.g. HiDef video capture) map their buffer memory into your address space for easy access - which can be as large as 512MB!
Yes, more address space is needed even more than more physical memory.
Why would anyone engrave "Elbereth"?