Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

AMD Says Barcelona Will Outperform Clovertown

Posted by kdawson on Sat Jan 27, 2007 06:59 PM
from the horse-race dept.
Dysfnctnl85 points out a ZDNet Blog posting in which AMD claims that its upcoming quad-core "Barcelona" chipset should be 40% faster than "Clovertown," Intel's quad-core Xeon 5300 line. AMD says that the introduction of Barcelona marks a shift in their strategy from emphasizing price to performance. The post goes on: "Intel is eager to claw back some of the server market share from AMD, and this is where Clovertown comes in... The Xeon 5300 line will represent excellent value for money since Intel plans on pricing them the same as its dual core Xeon 5100 processors. That could make things tough for AMD."
+ -
story

Related Stories

[+] AMD's Showcases Quad-Core Barcelona CPU 190 comments
Gr8Apes writes "AMD has showcased their new 65nm Barcelona quad-core CPU. It is labeled a quad-core Opteron, but according to Infoworld's Tom Yeager, is really a redefinition of x86. Each core has a new vector math processing unit (SSE128), separate integer and floating point schedulers, and new nested paging tables (to vastly improve hardware virtualization). According to AMD, the new vector math units alone should improve floating point operation by 80%. Some analysts are skeptical, waiting for benchmarks. Will AMD dethrone Intel again? Only time will tell."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by namityadav (989838) on Saturday January 27 2007, @07:05PM (#17786436)
    The way AMD and Intel are improving the processor speed is very impressive. I/O speed is going to become an even clearer bottleneck now.
    • I guess 4Gb FibreChannel, 2.5, 10 and 20Gb/s Infiniband aren't quite fast enough?

      I've managed storage for 15years and even within the largest datacenters very few host systems actually push their storage infrastructure. Most server admins say "I need linerate" b/c they have no idea how much data their applications will actually push. Plus it's a way to force the hba/hca/nic vendors to lower their prices.

      Btw: 80% of servers out there could run just perfectly fine with a pair of 1Gb/s fibrechannel HBAs.
        • Re: (Score:3, Informative)

          Latency is not a bottleneck.

          You could turn it around and say that, since the disks are not using their full bandwidth, the disks spend most of their time waiting for requests.

          That being said, disk latency is one of the major causes of poor performance. But "bottlenecks" only have to do with throughput.
          • by slamb (119285) * on Saturday January 27 2007, @09:31PM (#17787224) Homepage

            You could turn it around and say that, since the disks are not using their full bandwidth, the disks spend most of their time waiting for requests.

            Only by specious reasoning. I'll disprove by counterexample. If I continously tell the disk to seek to one extreme and read a cacheful, then seek to the other extreme and read a cacheful, it will neither be waiting for requests nor using its full bandwidth. A and not B disproves (A => B).

            Latency and throughput are unrelated only if there can be infinitely many requests produced and satisfied in parallel. In the case of a hard disk, there can be only one active request per head because it can only be at one place at once. Let's consider the example of my laptop hard drive [fujitsu.com]. It's rated at a data transfer rate of 150 MB/s. But look at the seek speeds - 1.5ms minimum, 12ms average read, 22 ms maximum. It can read a 1 MB file in 6.7 ms, but if that 1 MB file is fragmented into ten chunks across the drive, it'll take around 130 ms.[*] So in this case it actually transfers at 5% of its rated speed. And depending on the application, the data may be in many, many tiny chunks.

            That being said, disk latency is one of the major causes of poor performance. But "bottlenecks" only have to do with throughput.

            Latency limits throughput. The requestee usually can only satisfy a limited number of requests at once (see above), and the requestor may not be able to produce the next request until it's received the previous response.

            Simple example: I'm performing a binary search. I need to see what's at location mid before I know if I'll next be interested in location (low+mid)/2 or location (mid+high)/2. In some cases, I can do a speculative fetch for both locations, but you can only extend that out so many generations before you've used up most of your bandwidth on data you'll never use.

            Processors are smart about re-ordering instructions to keep working while they're waiting for stuff to happen, but still they frequently get to a point where they can't execute anything more because of ordering constraints - the results of some instruction are dependent on a previous instruction that hasn't completed yet because it's waiting for a value from memory. That value can be the actual instruction to be executed or an operand...either way, your shiny new processor's stuck doing nothing.

            [*] - It might beat the average if it's smart about ordering. At the very least, 22 ms has to get added if one request is at one extreme and one request is at the other extreme. That brings it down to 23% of the rated speed.

            • by Mad Merlin (837387) on Saturday January 27 2007, @10:42PM (#17787494) Homepage

              Let's consider the example of my laptop hard drive. It's rated at a data transfer rate of 150 MB/s.

              A SATA 1 interface can transfer at a maximum of 150 megs/s, but your hard drive can't. On sequential reads, you're unlikely to see much higher than 40 megs/s, even 7200 RPM desktop drives don't exceed 70 megs/s yet.

                • Re: (Score:3, Informative)

                  RAID 0 doesn't automatically ensure that both/all drives will read/write at the same time. In fact, RAID 0 is typically configured NOT to optimize that. Large interleave sizes, the ones typically used, optimize for multiple concurrent requests, not parallel throughput. Furthermore, each drive in a SATA system will get its own SATA link, so unless you are attaching a RAID 0 box via a single SATA link, your entire point is specious. Even if you had 2 RAID 0 drives with a small interleave attached via a si
          • The way I remember the definition of a "bottleneck", it's basically the lowest performance part that brakes everything else. It doesn't matter _why_ it's low performance. Just that less data gets through the bottle's neck than through everything else. If it brakes performance and other sub-systems have to wait for it, it's a bottleneck and that's that.

            Defining it as "throughput" is at best prestidigitation. The _real_ throughput is how much data actually gets through. No more, no less. The keywords being "a
    • Re: (Score:2, Redundant)

      The way AMD and Intel are improving the processor speed is very impressive. I/O speed is going to become an even clearer bottleneck now.

      Depends what you're using. I gotta say, I use PHP.. and I'm very happy with more cores coming on the server market, and CPU is quite clear bottleneck for that one technology :(
    • I think you meant to say "memory". 1 core gets an entire set of DDR2 controllers. 4 cores get... to share the same set of DDR2 controllers.

      More cores per socket, but the socket's DDR2 bandwidth stays the same. Let's hope your kernels fit in the L2/L3.
    • Unless you mean memory (where things don't look good ATM, as they seem to be expanding bandwidth but at the cost of adding latency), you might want to consider a flash drive.

      Flash has the advantage of having no seek latency, so even though I think current flash drives are slower than a hard disk as far as raw read/write speed is concerned, the seek latency cripples performance so much that a flash drive should be a massive improvement for most tasks. Most people don't do things like continously reading or w
  • by Original Replica (908688) on Saturday January 27 2007, @07:08PM (#17786462) Journal
    Everyone know that in Barcelona they take Ciesta. So don't plan on using you computer between noon and 1.
  • upcoming chipset? (Score:4, Insightful)

    by aczisny (871332) on Saturday January 27 2007, @07:11PM (#17786484)

    FTFS:

    "Barcelona" chipset should be 40% faster than "Clovertown,"

    You'd think since the blog got right that Barcelona is the upcoming processor from AMD, and since Clovertown is a processor codename from Intel, that the summary could have gotten it right too. Do submitters not read the articles either anymore?

      • Re: (Score:3, Informative)

        Check the subject line. Clovertown and Barcelona are codenames for CPUs, not chipsets. "Chipset" is used to refer to the chips used to support the CPU, not the CPU itself.
  • by j. andrew rogers (774820) on Saturday January 27 2007, @07:34PM (#17786664) Homepage
    Whether AMD or Intel is producing the fastest, cheapest, most scalable, or most efficient processor at the moment is not terribly important.

    What *is* important is that when you have two companies in genuine fierce competition at the bleeding edge of technology and performance, they extract an impressive amount of productivity and effort out of their engineering and science assets. Free markets are at their best when all the major players have a healthy fear of the capabilities of their competitors.
    • by Anonymous Coward

      ...if there was a similar competition in the OS market. You wouldn't need these mammoth processors in the first place. And having one would be a huge benefit, not a marginal one.

      • ...if there was a similar competition in the OS market. You wouldn't need these mammoth processors in the first place

        What makes you say that? What makes you think that there are the same kind of performance gains possible from an OS? What makes you think there is not competition?
        • Apple would get creamed if they did this. Most PC's out there have hardware that Apple does not have drivers for, by decoupling the OS from the hardware people would be able to pirate the OS, and of course Apple makes more money on the hardware they sell than the OS.

        • but not on the scale that an officially sanctioned PC-version of OSX would be.

          Officially sanctioned on what tiny subset of the PC hardware that's out there? Apple could never support the huge x86 hardware base out there, in fact a big part of their quality success comes from them having tight control on both the hardware and software aspects of their platform.

          Also they could never handle the tech support calls. "Why doesn't my ISA-bus hand-scanner from Windows 3.1 work on OSX?"
        • Apple should at least come with a mid-end desktop with a real video card as install base of normal PC's out there have good monitors that people reuse on new systems.
          also a $1500 laptop with real video will help them get more of the market.

          It's to bad the lintel chips forced them to have so few pci-e lanes in the mac pro.
        • Re: (Score:3, Insightful)

          Why doesn't Apple do this?
          Because then OSX would be just as troublesome as Windows and Linux. Apple's limited hardware support is a big part of why everything "just works."
  • AMD is growing (Score:3, Interesting)

    by adambha (1048538) on Saturday January 27 2007, @07:35PM (#17786668) Homepage

    AMD says that the introduction of Barcelona marks a shift in their strategy from emphasizing price to performance.

    While there are arguments both positive and negative toward the (somewhat) recent AMD/Dell alliance, this is one more indication that AMD is making even more progress in the processor market. Once considered the 'most bang for your buck' AMD is truly making a name for itself as a formidable competitor.

    One of the fundamental principles of capitalism is that competition spurs growth and progress. This is a case in point.

    • While there are arguments both positive and negative toward the (somewhat) recent AMD/Dell alliance, this is one more indication that AMD is making even more progress in the processor market. Once considered the 'most bang for your buck' AMD is truly making a name for itself as a formidable competitor.

      Actually, the way I remember history, AMD has only been "most bank for your buck" when it wasn't "best bang, period." As soon as it took the performance crown, an AMD computer (as in, once you also add the mo

      • Re: (Score:3, Informative)

        Then you must be new. AMD has basically been outperforming Intel ever since the 1.13Ghz PIII debacle. By Thunderbird and Thoroughbred in particular, AMD was outperforming the PIVs at about half the price. It wasn't until AMD64 that AMD started charging Intel prices. That's at least four years where AMD equaled or beat Intel performance for drastically less money (on the order of 50% price and often times less).
  • All Intel has to do is turn up the clock the day before Barcelona ships. We already know that the Core 2 Duo chips are very overclockable, and getting another 40% -- or even 50%+ out of them -- shouldn't be a problem.

    In fact I'll go further and say that buying any Intel (in my opinion, you fsking lawyers) before Barcelona launches is a Bad Move. It's seldom that performance increases by 50% in a calender year any more, as Mr. Steve Jobs found out a couple years back. This is not like the days when a 48

    • I think the overclockability is in part due to the fact that Intel likes to have generous safety margins. It might also be that going beyond a certain level goes above their power consumption rating. Increasing the clock would mean reducing those margins.
    • by be-fan (61476) on Saturday January 27 2007, @07:56PM (#17786806)
      All Intel has to do is turn up the clock the day before Barcelona ships. We already know that the Core 2 Duo chips are very overclockable, and getting another 40% -- or even 50%+ out of them -- shouldn't be a problem.

      The performance a chip can get with overclocking is way higher than what the manufacturer can deliver in final products. They have to be highly reliable at their specified clockspeed with (relatively) poor cooling, and while meeting the given voltage and thermal dissipation specifications. I've seen the Core 2 over-clock to 3.5 GHz (with conventional cooling) online, but how many of those are doing it at the stock Vcore while staying within the 65 watt TDP?
      • but how many of those are doing it at the stock Vcore while staying within the 65 watt TDP?

        You're assuming that Intel absolutely has to stay within those parameters. Expect them to step outside them the moment competitive advantage requires it. And they only have to do it with a few EE chips to claim the crown again.

        • by TheThiefMaster (992038) on Saturday January 27 2007, @08:50PM (#17787088)
          We are talking a SERVER line of cpus here. EE chips are a desktop cpu brand.

          For servers TDP is incredibly important, because server rooms are air-conditioned, a room full of higher TDP cpus costs much much much more to run from an electricity point of view.

          That's not to say that they won't overstep their vcore or TDP limits to get the upper hand on performance, but that wouldn't win them the performance/watt ratio crown that's the all-important stat for server cpus.
        • Re: (Score:3, Insightful)

          The TDP and voltage levels are part of the platform specification. Intel can't just up them without requiring motherboards, cooling units, etc, to be upgraded to handle the new spec. They might get away with it for some consumer level stuff, but not in the server market where Clovertown and Barcelona are competing. The server folks are going to want some substantial lead-time to rejigger everything to meet higher TDP and Vcore specs.
        • Expect them to step outside them the moment competitive advantage requires it.

          That would be, eight or twelve years ago. Or is it next year? Or do the facts show that they know they'd be creamed, and the PR disaster would make the Pentium floating point bug look like a company picnic?

          Personally, I think they know more about what they're doing than some overclockers. Have you ever read an Intel datasheet? Have you ever read ANY IC datasheet?

  • by trimbo (127919) on Saturday January 27 2007, @07:42PM (#17786718) Homepage
    Unless AMD employs completely incompetent morons as engineers, of course "Barcelona" should be faster than "Clovertown". Clovertown was released half a year to a year before Barcelona.

    The tables have turned. Even though Clovertown is not a "true" quad-core (aka a single die), Intel has a huge head start on AMD on quad core. Intel will be pushing forward with their 45nm technology and pushing out yet more models by the time these arrive. With their fabrication prowess, I would expect the gap to increase over AMD. Since dumping NetBurst, Intel is finally battling AMD in an sport they can potentially win.
    • Intel still has the FSB and that will get the way of the making the chips faster and add more IO.
      Havening 2 dual-cores linked by a fsb bus will get in the way even faster as the speed of the cpu gets higher.
      And a 4 cpu quad-core sever will likely choke up at the chipset to ram link as well as the chipset to chipset link.

      Also intels dael quad-core workstation and the V8 only haves has the pci-e lanes for 1 x16 slot and the 8 other ones are used for the chipset to chipset link amd based ones will blow it away
      • While all the technical reasons you listed are valid when looking towards future products, it is naive to think that Intel hasn't seen the same things you have. Intel does not employ stupid people (or at least for very long), so Intel will most likely have very good solutions to those problems by the time they are needed.
        • Like say... RAMBUS? Or maybe Monterey?

          Intel does in fact do very stupid things from time to time. The question is, is this one of them?
  • by sarathmenon (751376) <srmNO@SPAMsarathmenon.com> on Saturday January 27 2007, @07:57PM (#17786814) Homepage Journal
    I am a sysadmin, and I've seen super weight systems taxed to the extreme. The best servers don't boast of the fastest clock speed; they have the best i/o buses, tight integration of the hardware and software, and more importantly, reliability. These are the reasons I've seen that amd makes a better choice than Intel. Intel is all about FUD, increasing the clock speed at any cost and in general, very unreliable systems that act strangely when pushed under heavy processor load.

    I'd choose AMD over intel anyday - i've liked their strategies always, and in the server arena they are the best x86 player. But the bottom line still remains, sun's sparc line,ibm's ppc one and hp's rule. They have been in the business for quite some time, and they frankly know what they are doing.

    Intel, its not late to figure out the economics. Corporations choose the best machine for the job while running their servers. No one chooses cheap when they are shopping for their new database server. The big bucks are in the hell expensive servers, and not in the mom-and-pop line. You can sell 1,00,000 cheap servers instead of 1000 expensive ones. But the margins are higher ony in the latter.
    • I think you have a good point about other architectures. The problem with your post is, I have never had any problem with the reliability of Intel-based systems, even when running Windows, and even running dual Xeon systems running Netburst chips, my computers have been running cool and quietly. That, and Intel isn't necessarily about the highest clock anymore. I don't know if you've noticed, but they aren't promoting Netburst anymore either.
  • Mainly in FP (Score:5, Informative)

    by Visaris (553352) on Saturday January 27 2007, @08:54PM (#17787100) Journal
    This 40% faster than Clovertown claim is only referring to FP code. The integer side is not nearly as clear. Expect AMD to improve integer performance over K8, but I don't expect any miracles. Here is a small list of improvements Barcelona will have over K8:

    - Double L1 cache bandwidth
    - Double FP units
    - Single-cycle SSE (vs K8's 2-cycle)
    - More fast-path decoding
    - Double TLB size
    - Independent DDR channels
    - More cache (L3)
    - Out-of-Order loads
    - New instructions (LZCNT, POPCNT, EXTRQ/INSERTQ, MOVNTSD/MOVNTSS)
    - Double prefetch (from 16 bytes -> 32 bytes)
    - Larger Branch Target Buffer
    - Larger Out of Order (OoO) buffers
    - Support for new HT standard (3.0)

    • Re:Mainly in FP (Score:5, Insightful)

      by Erich (151) on Saturday January 27 2007, @11:39PM (#17787788) Homepage Journal

      New instructions (LZCNT, POPCNT, EXTRQ/INSERTQ, MOVNTSD/MOVNTSS)

      Interesting!

      I can't find much information on it, but I'm guessing "LZCNT" is count-leading-zeros. This is like "find-first-one" from the other direction. It's very useful for things like finding the magnitude of an unsigned numbers. It's used quite often on architectures without FPUs (like ARM) in floating point routines for renormalization. I guess it could also be useful if you are having to do floating point emulation for numbers with enourmous precision.

      I guess if you have "BSR" then LZCNT = -BSR

      POPCNT is probably population count, the number of 1s in a value.

      Both LZCNT and POPCNT are instructions that are a pain to do in software if you lack the instruction in the hardware, and they are relatively cheap (especially if you have BSF/BSR already).

      I'm still a bit suprised that there aren't a few more of these bit-banging instructions in x86, like bit interleave/deinterleave and bit reverse. Modern processors are doing enough signal processing work that one would think you'd thow the tools in the bucket, as cheap as they are. I guess lookup tables are good enough.

      What's the over/under for which SSE revision will add a galois field multiplier? 7? 8?

      But seriously, the dual ported caches are probably the best improvement for most people. You can't be too rich, too thin, or have too much memory bandwitdth.

      It looks like AMD has done the same thing Intel did with "Core 2"... just take a good architecture and keep making improvements... more issue width, more memory bandwidth, more flexibility in scheduling. Every bit counts.

      I think we're getting to a similar point in modern CPU microarchitectures to where we are in some other industries, where drastic improvements are much more rare and it all comes down to really great implementation... like making engines. There are some innovative ideas for engines, and certainly a lot of people experiment, but really the best designs are just really well balanced and tuned. (although more cylinders is usually a good thing for horsepower).

  • Obvious (Score:3, Funny)

    by Mazin07 (999269) on Saturday January 27 2007, @10:14PM (#17787380) Homepage
    Jeez, of course AMD's right. Take a look:

    Population of Barcelona: 1,673,075 [wikipedia.org]
    Population of Clovertown [google.com]: 5601 [census.gov] (or less)

    Barcelona is vastly superior.
  • by suv4x4 (956391) on Saturday January 27 2007, @10:55PM (#17787580)
    Intel's quad-core Xeon 5300 line. AMD says that the introduction of Barcelona marks a shift in their strategy from emphasizing price to performance

    The way they spun it, you can also claim they changed their strategy from slow to expensive.
    • Re: (Score:3, Informative)

      It's about time! But, why not drop the word "native" and admit they were engaging in deceptive advertising up to this point?
      Nice try, AMD hasn't been claiming any sort of quad-core processors - that's Intel:

      While Intel went for a design that crammed two dual-core processors into a single package, AMD have built all four cores onto a single die.
      (from TFA)
        • Re: (Score:3, Informative)

          Yes, there were four cores. Two cores on one chip, two cores on the other. They key words from the titles you quoted are "platform" and "multi-socket", neither of which imply a single die with four cores.
    • Re: (Score:3, Informative)

      AMD has yet to release a quad-core CPU. The whole QuadFX(aka 4x4) is a dual-processor system that is designed to be a consumer level platform that supports two processors. The reason for QuadFX to be worth looking at as a platform is that you will be able to swap out the two dual-core processors for two quad-core processors starting around the middle of 2007.

      AMD is really starting to hype their true next generation core design, not just quad-core. This is something that many people seem to be closing
      • by be-fan (61476) on Saturday January 27 2007, @07:46PM (#17786750)
        Linux is a preemptible kernel.
        • by MoralHazard (447833) on Saturday January 27 2007, @09:06PM (#17787150)
          Urm, that depends. Linux CAN be a pre-emptible kernel, if you compile it to be. There are various levels of pre-emptibility, depending on your needs. The in-kernel docs say that pre-emption is intended for desktop environments where perceived latency is a big deal, but servers will probably benefit from the lessened overhead of a non-pre-emptible configuration.

          But the original poster's comment is still bullshit. Windows Vista is a microkernel? What has THAT guy been smoking? Multi-core designs aren't that different from multi-CPU configurations, and we already know from experience that Linux hasn't been sidelined performance-wise.

          Actually, now that I think about it, the likeliest explanation is that the OP was just trolling.
    • Re: (Score:3, Informative)

      Since you were very snotty to someone who replied to you, I'm posting the snotty version of my reply... There is a point at which one must face facts. Since the AMD 64 line, AMD has had the superior cpu over the P4. The AMD line was, with few exceptions, cheaper, cooler, faster, and as stable, if not more so, and it did that while still including your precious protection against forgetting to put on the heatsink. Is that something you do often? Yes, the Athlon line was neck-and-neck with the P3, the At
    • by RzUpAnmsCwrds (262647) on Sunday January 28 2007, @05:31PM (#17792746)

      The day you can remove the fan and heatsink from a running AMD CPU and it will simply carry on running throttled down until the fan and heatsink are replaced, they will be ready for "professional" use.
      This just isn't true, nor is it really relavent. Intel CPUs do throttle if you have - say - a fan failure, but the throttling is not enough to keep the CPU stable without a heatsink.

      I have pulled the heatsink from an old Northwood, and, let me say this - the results are not pretty. The system crashed almost immediately.

      The Tom's Hardware tests you are probably referring to were pretty clearly faked.

      And, more to the point, when was the last time that you saw heatsink fell of of a system while it was operating? Fan failures, yes. Heatsinks falling off - not unless the box is dropkicked.

      The AMD was slightly unstable
      Was it? Tell that to the people who have been running Opterons successfully for years in server environments. Tell that to Dell, to HP, to Sun, to IBM, or to the millions of people who use AMD CPUs every day.

      One of the reasons AMD were cheaper, bang for buck, is they left out all the extra stuff Intel did not, like on chip thermal management so it didn't catch fire when the heatsink / fan failed.
      AMD CPUs have had on-die thermal management since Athlon 64, and chipset-implemented thermal management since the Athlon XP.

      Intel's thermal montior (TM1) feature has been the source of hell for lots of users. It's a good idea, poorly implemented - instead of halting the system or producing an error, the system continues to run - poorly. It makes it difficult to diagnose whether or not the heatsink is working properly, unless you use tools which detect throttling, which, unfortunately, aren't bult in to Windows.