Slashdot Mirror


AMD Says Power Efficiency Still Key

Larsonist writes to tell us that even though AMD's new architecture wont be released until mid-2007 they are still letting people in on what some of the new features will be. From the article: "While clock speeds have not been revealed, each of the four cores will integrate 64 KB L1 Cache and 512 KB L2 cache. The native quad-core architecture will also include a 2 MB shared L3 cache, which may increase in capacity over time. The processor will have a total of four Hypertransport links - up from three today - that provide a total bandwidth to outside devices of 5.2 GB/s. AMD is also thinking about integrating support for FB-DIMMs 'when appropriate.'"

167 comments

  1. Almost obligatory statement... by Pharmboy · · Score: 5, Interesting

    But will it run Vista? (j/k)

    Is Vista going to support 4 cores, or like XP Pro and 2k, limit it to 2 "cpus" so they can charge more for the server version?

    --
    Tequila: It's not just for breakfast anymore!
    1. Re:Almost obligatory statement... by adisakp · · Score: 4, Informative

      MS licensing is for currently for physical CPU's not for cores. Right now a dual xenon (two CPU's) counts as two CPU's in MS licensing terms but a dual-core (two CPU's within a single die or processor socket) is one CPU under MS licensing terms.

      In other words, MS counts sockets, not cores.

    2. Re:Almost obligatory statement... by Virtex · · Score: 2, Funny
      But will it run Vista?
      Sadly, no. By the time Vista comes out, AMD and the rest of the world will have long since moved beyond quad-core processors.
      --
      For every post, there is an equal and opposite re-post.
    3. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      MS licensing is for currently for physical CPU's not for cores. Right now a dual xenon (two CPU's) counts as two CPU's in MS licensing terms but a dual-core (two CPU's within a single die or processor socket) is one CPU under MS licensing terms.

      That is true for winXP and win2003, but not for win2000 (all versions). Win2000 can't tell the difference between multiple processors & multiple cores.

    4. Re:Almost obligatory statement... by adisakp · · Score: 1

      True and that's why I said "currently". At the time of Win2000 there were no multi-core single-socket CPU's that ran the OS.

    5. Re:Almost obligatory statement... by Pharmboy · · Score: 3, Interesting

      If I remember right, there was some controversy with Oracle considering a dual core as two cpus, and they backed off. If we see 4 or more cores, the need for multiple sockets goes down, and I just wonder if MS will reconsider this licensing to prevent "lost revenue".

      --
      Tequila: It's not just for breakfast anymore!
    6. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      A better question is will is not if it will run XP, but will it viruses

    7. Re:Almost obligatory statement... by dfinster · · Score: 3, Insightful

      Really interesting question. For my entire career (since 1983), hardware has outrun software, and OS software in particular. This is a new and interesting twist. Extracting money from users based on "number of processors" or "processor power factor" (think Oracle) may become more difficult in a world of muti-core, multi-die, and multiple architecture.

      For example, which is worth more (none of these CPUs exist) - a quad CORE 2 or a eight core Athlon XP?

      I'd expect the eight-way to be better at some tasks that are easy to multi-thread, perhaps database servers. I'd expect the quad CORE 2 to be better at most general tasks, mostly because current OS and compilers aren't designed for multiple cores.

    8. Re:Almost obligatory statement... by Anonymous Coward · · Score: 5, Informative

      Microsoft will not charge per core anytime soon. They might have a dominating position on the desktop, but when it comes to servers, they're fighting tooth and nail to get a position of respectability, let alone dominance.

      So, let's look at the two markets seperately.

      Desktop, the users are likely to not care too much, provided the "Per core" cost is low enough. When we start seeing 4/8/16 core CPUs, a $10 per core fee will add up quick, but most home users will be using OEM copies and won't see that cost. Most business will have site licenses and won't care. But, some home users will, and some businesses will care, and they'll seriously consider alternatives (Maybe, maybe not switching). Microsoft would much rather "lose" money by not fleecing people, than have them even CONSIDER switching, so management's going to ditch the idea for desktops and workstations.

      Server market... they need any advantage they can get. They main competition is Solaris, BSD, and Linux. Linux and BSD are *free*, and Solaris has a bunch of good features which are pretty much Solaris only, even still. Charging per core would be suicide in this market, too.

      So, what market would charging per core be a good idea for Microsoft? None. Say what you will about their software writing abilities, but nobody should doubt their marketing prowess.

    9. Re:Almost obligatory statement... by gmack · · Score: 2, Interesting

      I'm going to guess not very well at first. With all 4 cores having the abillity to run at different clocks speeds I doubt this qualifies as SMP anymore.

      Most SMP code is tested on CPUs of equal clock speeds so odds are this is going to bring out all sorts of fun race conditions in Vista, Linux and *BSD and I'm personally not so sure I'm going to touch this until the resulting dust settles.

      I'm not saying it's a bad idea.. it looks like a good one but this will take time for the software to mature.

    10. Re:Almost obligatory statement... by Millenniumman · · Score: 1

      Their marketing is poor. Remember the "if Microsoft designed the iPod box" contest?

      At this point, they are the de facto standard, so they don't need good marketing.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    11. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      For my entire career (since 1983), hardware has outrun software, and OS software in particular

      You were sheltered. I wrote and encountered plenty of programs that outran the hardware capacity. I wrote some for the forthcoming quantum computers.

    12. Re:Almost obligatory statement... by cecil_turtle · · Score: 3, Interesting

      I agree that Microsoft (or likely anybody else) won't change to a per-core pricing model, but for different reasons. The point of per-CPU pricing is just to determine the market - the type of user/computer:

      1 CPU = most laptops and desktops, low end servers
      2 CPU = high-end workstations, average servers
      4 CPU = high-end servers

      As the number of cores ramp up, as you said to 4/8/16, then charging per core would be like charging per GHz or per L2 cache size - it doesn't make sense, adding cores will just be another way that new chips get faster than old ones. But the number of actual CPUs/sockets to define a specific market will likely stay the same for some time. Other than the Oracle debacle that grandparent poster mentioned, all per-core pricing theories have just been speculation. I can't imagine any company successfully pulling that off.

    13. Re:Almost obligatory statement... by maraist · · Score: 3, Informative

      Most SMP code is tested on CPUs of equal clock speeds

      You're kidding right? I can't imagine any software which depends on the timing of coperative CPUs.. MPI and general divide-and-qonquer work-clusters could care less about the performance level of peer threads/co-processes. Hell process interrupts due to pre-emptive multi-tasking is enough to guarantee lack of symmetry.

      Now perhaps you're referring to scheduling problems in the kernel.. I'm sure that AMD would be generous enough to provide kernel patches as are necessary.

      --
      -Michael
    14. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      In other words, MS counts sockets, not cores.

      How do you know? They can change licensing terms at anytime. You did read the EULA, right?

    15. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      I must question your logic here.

      What does their design ability being bland for the most part (Which is what the "iPod Box design" video was about) have to do with marketing?

      I'll give you a hint: Not much.

    16. Re:Almost obligatory statement... by eggoeater · · Score: 4, Informative
      but when it comes to servers, they're fighting tooth and nail to get a position of respectability, let alone dominance.
      Are you kidding?
      I work for a very LARGE bank. I guarentee you we have more boxes running MS Server 2003 than all others combined.
      We have some HPUX, IBM, and SUN sprinkled in there but several of the vendor apps I've worked with lately has dropped all support
      for SunOS and is now requiring Windows Server for their apps.
      We use to run Novel for our file servers but that was dropped for MS Active Directory.
      The next leading server OS we use is probably zOS. No Linux yet but I know the powers-that-be are looking at it.
      (BTW, I'm no MS fanboy, I'm just making a point.)

      I'm sure there are many industries in which MS does not have the majority of the server market but
      large financial groups are not among them.

    17. Re:Almost obligatory statement... by adisakp · · Score: 2, Informative

      SMP means the processors are similar (i.e. can run identical binary code). They do not need to run in lock-step synchonization to be SMP. Indeed, it is currently possible to halt a single processor in a dual processor system (two sockets) so a similar case already exists in current SMP systems.

    18. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0, Flamebait

      I'm sorry, but how does your anecdotal evidence of a single company change the fact that the majority of servers are not Windows? Microsoft was recently celebrating the fact that they hit the 25% mark for server sales (for a single quarter), and last I checked, 25% wasn't even a plurality in the server market.

    19. Re:Almost obligatory statement... by Nutria · · Score: 2, Funny
      we have more boxes running MS Server 2003 than all others combined.

      Is that because you need more Server 2k3 boxes to get the job done?

      --
      "I don't know, therefore Aliens" Wafflebox1
    20. Re:Almost obligatory statement... by eggoeater · · Score: 4, Informative
      I'm sorry, but how does your anecdotal evidence of a single company change the fact that the majority of servers are not Windows? Microsoft was recently celebrating the fact that they hit the 25% mark for server sales (for a single quarter), and last I checked, 25% wasn't even a plurality in the server market.
      I wasn't saying they have a majority overall, just in my company.
      I was giving an example to counter the GPs claim that MS doesn't have respectability in the server market.

      Not only do they have respectability, I see more and more vendors requiring them and most custom apps we write is on MS (desktop and server), although a lot of our web stuff is IBM (websphere, etc).
      I work in telecommunications; Aspect, Avaya, Cisco (not cisco routers/switches) have ALL migrated from other OSs to MS in the past 5 years for their server and desktop apps.

      Yes, Novel, Sun, HP, and IBM are huge in the server business. Except for IBM, they will steadily lose share to MS over time.
      One of the main reasons this hasn't happened faster (like in the desktop arena) is because there are a LOT of home-grown apps that companies have built over the past 15 years that still require a particular OS to use.
      At the bank I work for, we have a home-grown desktop app that is "critical". It was originally written for OS2. Around 1997 the team was forced to port it to MS windows NT.
      The conversion was brutal and it took them forever to get all the bugs worked out.
      Cut to 9 years later. WERE STILL USING THAT APP! (and no one is happy about it.)
      They've tried 4 times in the past 5 years to either have it rewritten or replaced with a vendor product, but every project has failed.
      It's so bloated and patched it's a nightmare to maintain, but even tougher to replace.


      Now apply that story to the thousands of custom server apps in thousands of companies around the world that only run on SunOS, HPUX, Novel, etc.
      The number of custom web apps alone that have been written on Sun servers could keep that company going another 20 years.
      We run a lot of MS server OS at work because we've been busy migrating stuff over the past 5 years. (a LOT of stuff.)

      So, my point is, MS Server OSs are not only respectable, but many large companies are actively moving towards them because they see it as streamlining. (Large companies like to be consistent and stick to "industry standards", even if it doesn't make good business sense.)
      MS knows it's going to take time; it's not like replacing a desktop OS.


    21. Re:Almost obligatory statement... by morcego · · Score: 1

      Actually, SMP means the processors are symmetric, which has deeper implications than simply similar.

      Lets also remind that SMP is Intel's way of doing multiprocessing. AMD's is called simply MP, and is a very different beast, already having different code on the Linux kernel.

      That being said, as long as we are already outside the SMP concept (we are talking about AMD here), I doubt different clock speeds will be much of an issue. Specially since much of the MP code on the Linux kernel already uses spinlocks that should be able to (mostly) take care of it.

      --
      morcego
    22. Re:Almost obligatory statement... by Joe+The+Dragon · · Score: 1

      They should move home to 2 cpus and Business / Ultimate to 4

    23. Re:Almost obligatory statement... by eggoeater · · Score: 3, Interesting
      Is that because you need more Server 2k3 boxes to get the job done?
      Outside of the obvious joke, this is actually true, but probably not for the reasons you think.

      Real reason: politics. One of the problems with server apps is that they tend to be "critical" to normal operations of the business.
      This means if you tell someone, "Hey, your server is under-utilized so were going to put this other groups app on there...",
      the shit is definitely going to start flying. (ex. "that server came out of my budget..." etc.)

      Ask anyone where I work (or probably where anyone works) and they would say that it would be the end of the world to have to share a server.
      In truth, it's all too easy for someone to mess up and bring a server to it's knees.
      The group I work in, we have probably 80 servers (yes, they all run MS), and none of them can be shared because it violates the SLA we have with Cisco. They won't support the app if anything else is running on the server.
      (Cant say I entirely blame them.)

      They solution to this problem is virtualization; I've been telling my co-workers that the future of servers is virtualization.
      Until we can really make it work politically, we'll be running racks and racks of servers that mostly run 90+ percent idle.

    24. Re:Almost obligatory statement... by be-fan · · Score: 2, Informative

      Symmetric doesn't really have any deeper implications. It just implies the processors are similar. There's no underlying implications about synchronization. When writing code for SMP machines, not only is it not possible to accidentally depend on the processors being synchronized, it's impossible to explicitly depend on synchronization.

      Spin-locks or not, cores running at different clockspeeds aren't going to expose any more race conditions than regular usage. Even on a current SMP system, the processors will almost always be asymetrically loaded, so threads of an app won't really see the two processors running at the same speed anyway.

      --
      A deep unwavering belief is a sure sign you're missing something...
    25. Re:Almost obligatory statement... by morcego · · Score: 1

      Care to show me a 3-way SMP system, with similar processors ?

      But I agree there the "other" implications for symmetric are mostly hardware related, even tho some of them reflect on software (OS) design.

      --
      morcego
    26. Re:Almost obligatory statement... by Anonymous Coward · · Score: 2, Insightful

      Poster of the post you originally replied to here... Read my post more carefully. I didn't say that their OS wasn't 'respectable', but that their POSITION wasn't respectable. Their overall position in the server market is abysmal, something like 10-15%. And, like a first year marketing student can tell you (And will. Oh god, they won't ever stop babbling...) mind share matters. When IT managers think "Server", they generally think UNIX, and will look at UNIX solutions first, (Unless it's something like an Active Directory or Exchange server). The market position they have simply isn't respectable. If it were, when the CTO was thinking "server", it wouldn't be "What type of UNIX" it would be at LEAST "Should I go with UNIX or Windows". This doesn't mean that there are no companies, or even industries, where that's not the case, but overall that's how the market stands.

    27. Re:Almost obligatory statement... by hackstraw · · Score: 3, Interesting

      "processor power factor" (think Oracle)

      I'm not sure if Oracle still does this, but they used to have almost voodoo math to figure out how much you owe oracle. It was something like X/CPU, then that value multiplied by a scale for the type of CPU (at the time RISC vs CISC), and then another multiplier by the amount of RAM on the box.

      When I heard that, I always suggested under specing the box and then silently upgrading it after the Oracle guys left. I believe the technical term is sliding scale which means the more you can afford, the more you will pay.

    28. Re:Almost obligatory statement... by repvik · · Score: 0

      I'm sure there are many industries in which MS does not have the majority of the server market but
      large financial groups are not among them.


      Time to withdraw all my money and put them in the mattress ;-)

    29. Re:Almost obligatory statement... by Henry+V+.009 · · Score: 1

      A Java programmer, I take it?

    30. Re:Almost obligatory statement... by jelle · · Score: 2, Insightful

      "and none of them can be shared because it violates the SLA we have with Cisco."

      But _that_ is not politics, it's because Cisco understands windows servers and how badly they handle more than one task.

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    31. Re:Almost obligatory statement... by chris_eineke · · Score: 1
      the more you can afford, the more you will pay.
      You're looking for price discrimination.
      --
      "All you have to do is be fragile and grateful. So stay the underdog." Chuck Palahniuk, Choke
    32. Re:Almost obligatory statement... by catacow · · Score: 5, Informative

      SMP means the processors are similar (i.e. can run identical binary code). They do not need to run in lock-step synchonization to be SMP.

      The Symmetric in SMP refers to the fact that each process can run the same tasks.In an assymmetric setup, there may be a processor dedicated to the kernel or other tasks.

      It most definitely has nothing to do with speed.

    33. Re:Almost obligatory statement... by pchan- · · Score: 3, Informative

      Now perhaps you're referring to scheduling problems in the kernel.. I'm sure that AMD would be generous enough to provide kernel patches as are necessary.

      I find that the two processors in my dual-core Athlon X2 run at slightly different speeds (according to AMD, this is expected). That in fact did cause the Linux kernel some problems, since it was trying to balance handling the interrupts between the two. The problem happened when the timer interrupt bounced between the two, as within an hour or two of startup their tick counts became significantly separated. This made the system clock start running forward at a rapid rate. A Linux patch fixed this issue. So I can definitively say that Linux does run on SMP cores at different speeds.

      I'm not sure how Windows will do it, but they'll probably figure it out if they haven't yet. The real challenge is a new scheduling algorithm for variable CPU capabilities (although we do have that to some extent with frequency scaling on single CPUs).

    34. Re:Almost obligatory statement... by gnasher719 · · Score: 1

      '' I agree that Microsoft (or likely anybody else) won't change to a per-core pricing model, but for different reasons. The point of per-CPU pricing is just to determine the market - the type of user/computer:

      1 CPU = most laptops and desktops, low end servers
      2 CPU = high-end workstations, average servers
      4 CPU = high-end servers ''

      Nice that the MacBook I bought is a high-end workstation.

    35. Re:Almost obligatory statement... by mdhoover · · Score: 1

      Yeah, just dont put Oracle on the box, their core licensing policy suggests Larry Ellison needs a new yacht (the $200M one he currently has just isn't good enough)

    36. Re:Almost obligatory statement... by feepness · · Score: 1

      I believe the technical term is sliding scale which means the more you can afford, the more you will pay.

      Damn Socialists are everywhere nowadays I tell you!

    37. Re:Almost obligatory statement... by Heembo · · Score: 1

      I'm sure there are many industries in which MS does not have the majority of the server market butlarge financial groups are not among them.

      I hate to agree with your logic, but you are right on. And I would go even further than that, MS rules the big finance companies on the desktop as well in more ways than one.

      I have a client who is a high-end billion-dollar equity fund who is paying me out the nose to write VBA for EXCEL for them! I let them know I'm a J2EE guy, I'm a web applications architect, I'm a data engineer - but they begged and begged more for me to write an excel app for their VP of Something that would just hit the database directly from Excel.

      I begged them back, anything but that, but they paid me off, ya see
      May the gods all forgive me. But take excel away and I bet the world markets would collapse!

      --
      Horns are really just a broken halo.
    38. Re:Almost obligatory statement... by eggoeater · · Score: 1

      Agreed. I was just trying to make another point about server under-utilization.
      Virtualiztion will allow a MIN and MAX amount of CPU power to go to each machine.
      Cisco doesn't allow for that as an exception to the SLA, but they should.


    39. Re:Almost obligatory statement... by lumber_13 · · Score: 0

      640K should be enough for anybody -- with love Bill

    40. Re:Almost obligatory statement... by Carewolf · · Score: 1

      CPU scheduling assumes the processors are equally fast. This was one of the problems with hyper-threading. The second virtual CPU sucked and the scheduler didn't always know leading to poor performance.

      Making the scheduler efficient on a multi-speed machine, is less than trivial.

    41. Re:Almost obligatory statement... by legoburner · · Score: 1

      For those that dont remember or have not seen it, if Microsoft designed the iPod box.

    42. Re:Almost obligatory statement... by Nutria · · Score: 1
      Until we can really make it work politically, we'll be running racks and racks of servers that mostly run 90+ percent idle.

      And geeks wonder why MSFT is gaining market share and has 100 jillion dollars in the bank...

      --
      "I don't know, therefore Aliens" Wafflebox1
    43. Re:Almost obligatory statement... by FellowConspirator · · Score: 1

      Compare that to the pharma, biotech, and chemical industries where dependence on Windows is the kiss-of-death. Certain segments of the telecom sector are the same way today. The financial industry is Microsoft's last bastion (and even then, most of the exchanges have moved to Linux or UNIX).

    44. Re:Almost obligatory statement... by rbarreira · · Score: 1

      Any examples or references?

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    45. Re:Almost obligatory statement... by eggoeater · · Score: 1

      Of course, the mainframes do all the account processing.
      Account numbers and customer info very rarely get copied anywhere else,
      and if it does, the internal data security teams constantly do audits.

    46. Re:Almost obligatory statement... by AvitarX · · Score: 1

      Which Mac Book has 2 CPUs?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    47. Re:Almost obligatory statement... by Paul+Jakma · · Score: 1

      Care to show me a 3-way SMP system, with similar processors ?

      Upgrade one CPU in a two single-core SMP machine to a dual-core. (Quite possible with Opterons).

      --paulj

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    48. Re:Almost obligatory statement... by IamTheRealMike · · Score: 1

      So do you work for a bank or in telecoms?

    49. Re:Almost obligatory statement... by adisakp · · Score: 1

      FWIW, I program low-level hardware on video game consoles so I do lots and lots of MP programming (on custom chips). I've written code on multi-CPU designs from the Sega Saturn (2 CPU), the Atari Jaguar (3 CPU's - 1 CISC / 2 RISC), PS2 (2 RISC CPU's EE/IOP + 2 DSP's VU0/VU1) not to mention tons of weird custom chips and hardware in various systems. I am also developing on XBOX360 (SMP) and PS3 (which is primarily Assymetric if you don't count the "hyperthreading" on the PPU).

      The Symmetric in SMP refers to the fact that each process can run the same tasks.In an assymmetric setup, there may be a processor dedicated to the kernel or other tasks.

      I was referring to the symmetry on a hardware level, not software. In an SMP system, you have processors that can run identical binaries (the same tasks). Here you are in agreement with me, just stating it differently. It's possible to take any SMP hardware and write an OS or software for it that explicitly schedules specific tasks to certain CPU's which uses the hardware in a non-Symmetric manner but when we refer to Assymetric MP on a hardware level, there are usually physical differences between the CPUs (again, my example of binary compatibility - which is common in game consoles) or the CPU's are nearly identical but connected to resources in a non-Symmetric manner (i.e. the VU0 and VU1 on the PS2) so they require differenct tasks to be sent to each one.

      To me SMP and ASMP is more important to examine from a hardware level than from the software design. This any system that can run SMP from hardware can be made into an ASMP system using software, while a system that is truly ASMP from a hardware design may be anywhere from just very difficult to physically impossible to run as a SMP system in software.

      It most definitely has nothing to do with speed.

      This point is also 100% in agreement with what I said. My whole post was that speed or lock-state execution wasn't necessary for SMP, just the ability to run similar tasks (i.e. identical binaries).

    50. Re:Almost obligatory statement... by dan+the+person · · Score: 1

      I work for a very LARGE bank. I guarentee you we have more boxes running MS Server 2003 than all others combined.

      It can't be a very large bank if one person knows what OS is installed on all the banks servers.

      I have enough trouble keeping track of the servers required to run our one application. Let alone keeping track of every server used by every application in each of dozens of subsiduaries across 80 operating countries.

    51. Re:Almost obligatory statement... by morcego · · Score: 1

      And since Opterons are MP, and not SMP, what is exactly your point ?

      --
      morcego
    52. Re:Almost obligatory statement... by Paul+Jakma · · Score: 1

      Despite all the blather in this thread, Opteron are SMP machines, by general definitions anyway. Many of the posters in other threads appear to be confused between AMP and ccNUMA.

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    53. Re:Almost obligatory statement... by jmauro · · Score: 1

      All of them.

    54. Re:Almost obligatory statement... by notoriousE · · Score: 0

      XP Pro will support dual dual-core opterons (four cores) just fine --- i think you are misinformed

      --


      And then there was E
    55. Re:Almost obligatory statement... by mdhoover · · Score: 1

      Depends on the industry.
      Mission critical 5 9's required? NOT going to go on tinker toy wintel boxes.
      Needs to be robust? Uptime is important? Again, not going to go on wintel.
      Needs to be secure.... this goes without saying.
      Needs to run highly multithreaded apps... thats going to unix (most likely solaris), not wintel.
      Need a big kick-arse database server? running SAP, Oracle Financials or the like?... you would be insane to put it on wintel.

      Sure for web services (sitting behind a hardened reverse proxy) wintel can be found, and for SMB file servers or other desktop support services, sure, but "actively" moving towards wintel... more like only if they have no other choice.

      See folks like their unix boxes, they install them, put their software on them, then shove them into the back of the server room and ignore them for the next 3 years until either the lease runs out, the box needs critical security fixes (most often no reboot required unless it is kernel related) or some (fully redundant) piece of hardware needs replacement. They bring guaranteed peace of mind.

      Note: I am somewhat biased, true. I provide consultancy to large corporates, sometimes on behalf of Tier 1 hardware vendors. I just calls it as I sees it (lets just say work is very busy at the moment)

    56. Re:Almost obligatory statement... by TheThiefMaster · · Score: 1

      The problem isn't technically the cpus running at different speeds, it's the cycle counters being out of sync and a thread that reads the cycle counter (normally for super-accurate timing) being shuttled between the cpus. Obviously this can only happen in a multi-core system and not a cluster, unless it's a cluster of multi-cpu machines, in which case the multi-cpu nodes have trouble not the whole cluster. Having different speed cpus in a system causes two problems: A program could read different cycle counters and suddenly decide that many hours have passed (or it's jumped back) since it last read the counter, and/or it will see time running at a different rate depending which cpu it's on as their cycle counters increment at different speeds.

      The source dedicated server (mostly for counterstrike source) uses the cycle counter for timing, and it goes absolutely haywire in a mismatched cpu system (at least on windows). The most obvious effect is that the uptime counter can't make up it's mind about how long the server's been up, but there are movement prediction etc errors too.

      For more fun try running counterstrike source (itself, not the server) on an amd X2 system with cool & quiet on and without the windows patch. CS will read the speed of your cpu at the low-speed setting when it starts, then when the cpu switches to high speed it'll run twice as fast as it should and also make you move twice as fast from everyone else's pov. Strangely when this happened to me months ago I didn't get any warning from VAC, even though the server was secured. Personally I think moving twice as fast as everyone else is a hack, but what do I know?

      Other than these two, I haven't seen a single program using the cycle counter for timing, but that doesn't mean that there aren't loads and loads of them around.

    57. Re:Almost obligatory statement... by Anonymous Coward · · Score: 0

      I think you're getting CPUs and cores mixed up. CPU = processor = 1 physical socket.

  2. Power control at the per core level by adisakp · · Score: 4, Informative

    The article is very light on details but the one picture implies power control at the core level. For example if core-1 is running a 100% workload and core-2 has a 50% workload, core-3 and core-4 can be halted resulting in a power load of only 45% the total 4-core max load.

    1. Re:Power control at the per core level by Anonymous Coward · · Score: 0

      37.5% total load.

      25% per core at 100% capacity. a core at 50% capacity would be half 25% or 12.5%... 37.5% total.

    2. Re:Power control at the per core level by adisakp · · Score: 5, Informative

      25% per core at 100% capacity. a core at 50% capacity would be half 25% or 12.5%... 37.5% total.

      Mathematically that's what you'd expect but 50% CPU load doesn't mean 50% the power - it completely depends on what state a 50% load puts the CPU in (lowered clock or same clock / sleep-state during idle / etc). Plus you have to remember that a halted-state CPU still consumes more power than a CPU that is completely powered down. This is why it takes 45% rather than 37.5%. You can't apply such simple principals to power calculations.

    3. Re:Power control at the per core level by QuantumFTL · · Score: 1
      From this article:
      The key to achieve this goal is AMD's single-die architecture and its ability to individually adjust the clock speed of each processor core. For example, if the full processing power of all four cores isn't needed, the architecture is able to reduce the clock speed of individual cores. One core running at full speed and three cores at one third of their maximum clock speed would drop power consumption by 40%. AMD can even completely shut down individual cores for even greater reduction of the CPU's power consumption.
    4. Re:Power control at the per core level by undeaf · · Score: 1
      One core running at full speed and three cores at one third of their maximum clock speed...
      That's possible? Since when? I though it was called symetrical multi proccesing for a reason(with some exceptions, like different cache sizes being okay). If it doesn't have to, then does the second core actually have any good reason to be able to run at same speed as the first?
    5. Re:Power control at the per core level by ashridah · · Score: 4, Informative

      It's definently possible. Make sure the 'Cool-n-Quiet' junk is enabled in the bios on any recent AMDx2 system, and install powernowd or something similar under linux.

      My cpu speeds idle at around 1GHz, and then spring back up to 2.4GHz when under load, then slowly drop back to 1GHz when not in use. Independently, I might add.

    6. Re:Power control at the per core level by Unnamed+Chickenheart · · Score: 1

      Also there is that L3 cache and most likely some common logic that will consume power even if all the four cores are idle?

      --
      urd
    7. Re:Power control at the per core level by undeaf · · Score: 1

      In that case, why do they run at the same maximum speed anyway? Throtling only reduces the power usage, it does not reduce TDP, ie. the amount of heat the heatsink has to be capable of disipating. If the second core had a maximum voltage that was a bit lower, that could allow the heatsink to be cheaper or quieter, or for the first core to use more power. And then there's the question of whether both cores have the same speed limits at a certain voltage, maybe most current 2x2.6ghz cpu's are capable of doing 2.8&2.6 at the currently used voltage.

    8. Re:Power control at the per core level by MoOsEb0y · · Score: 1

      I can't speak for the Athlon 64 X2, but I know for a fact that Core 2 Duo dynamically turns off blocks of L3 cache that aren't needed.

    9. Re:Power control at the per core level by Anonymous Coward · · Score: 0
      I know for a fact that Core 2 Duo dynamically turns off blocks of L3 cache that aren't needed

      Right. The only problem being that it can't turn them on in the first place, since Core 2 Duo has no L3 cache. You probably meant L2. And yes, it's a nifty trick for power saving.
    10. Re:Power control at the per core level by morcego · · Score: 1
      That's possible? Since when? I though it was called symetrical(sic) multi proccesing


      No. It is only called Symmetrical (SMP) on Intel processors. AMD's multiprocessing architecture is somewhat different.
      --
      morcego
    11. Re:Power control at the per core level by Wdomburg · · Score: 1

      That's not what symmetric means in this context. It merely means that the processors have equal access to a shared memory address space. The Opteron is actually a NUMA architecture (non-uniform memory access), thanks to the integrated memory controller. Each processor has it's own memory bank which it can access faster than the others in the system.

      Technically there's no reason a system could be built with different speed processors. Likely the reason it's not typically supported is because there's little reason for it and it complicates scheduler design. In this case the cores would be identical in their potential speed, which simplifies things.

    12. Re:Power control at the per core level by Anonymous Coward · · Score: 0

      My P4 used to be able to go from 2.6GHz down to 333MHz in steps of 333. For some undocumented reason the newer linux kernels crippled it and don't support lower than 2.3GHz.

    13. Re:Power control at the per core level by Anonymous Coward · · Score: 0

      Independently? Are you sure? The current CPUs aren't supposed to support that. The multiplier is the same for the both cores; CnQ lowers Vcore and multiplier on both cores, it cannot be done independently.

  3. But will it... by corychristison · · Score: 3, Insightful

    ... run OS/2?

    Joking aside, lately I've been pondering AMD's next move in the everlasting Intel vs. AMD chess game.

    I'm here for hoping they can pull ahead again and force Intel to do the same.
    Always Remember: competition is good!

    1. Re:But will it... by timeOday · · Score: 1

      Yes, and the real takehome message from this "announcement" is that AMD has no answer to Intel for the next year. That is a long time to be coasting! Noobody is going to put off an upgrade due to such a long-term milestone, so I wonder why they even bothered putting it out there.

    2. Re:But will it... by (negative+video) · · Score: 1

      Yes, and the real takehome message from this "announcement" is that AMD has no answer to Intel for the next year.

      Or it means that AMD's true answer is not yet announced.

      Noobody is going to put off an upgrade due to such a long-term milestone, so I wonder why they even bothered putting it out there.

      Exactly. If you make an announcement that causes your customers to put off purchases, you lose current sales. (The paradigm being Osborne, whose preannoucement of the next version was so successful that they went broke before it could be finished.) The two viable choices are to keep totally quiet, or boost awareness without wrecking sales.

    3. Re:But will it... by TheLink · · Score: 1

      Well the problem AMD has is if they don't announce, people could go "Core 2 Duo".

      I suggest it's better for AMD to lose some sales to their "future" than to Intel.

      Especially given that so far historically you are more likely to be able to upgrade an AMD system meaningfully than an Intel system. So if AMD announces a nice shiny future, people might still buy an AMD _now_ that is slower than a Core 2 Duo, in hope of being able to upgrade to the next AMD stuff.

      Whereas Intel's new stuff just tends to not work with their old chipsets/sockets/memory etc. If you buy Core 2 Duo now, the odds of you being able to easily upgrade to some new Intel CPU next year is pretty slim.

      So it doesn't look good for AMD.

      It's just like the past few years when Intel had no answer to AMD's opterons - they just had crappy P4 stuff. Intel lost quite a bit of share to AMD because of that.

      --
  4. 128KB L1 by tomstdenis · · Score: 1

    64K code+data.

    Not 32/32.

    Tom [not official...]

    --
    Someday, I'll have a real sig.
  5. Re:Irony by SilentOneNCW · · Score: 1

    Well cover me in egg and flour and bake me for 14 minutes!

  6. Translation: "Ignore performance" by Anonymous Coward · · Score: 0

    In other words, we can expect the quad core AMDs to still get throughly spanked by Intel's Core Duo technology as far as performance goes. Not that it's necessarily a bad thing, extra performance may not be necessary and the power savings may make it simply more cost effective.

    Of course, most people purchasing server technology probably won't care about power consumption. It's not their budget being wasted on power, it's some other overhead account they don't have access to.

    I expect AMD is trying to work to convince people that their lower power consumption is worth the performance lost over using an Intel part. Sort of like the "megahertz myth", but instead more of a "total cost of ownership" deal. Like how Microsoft explains that Linux is REALLY more expensive than Windows, or something.

    I really have no idea where I'm going with this. Hopefully someone can figure out WTF I'm talking about and make it coherent. :-)

    1. Re:Translation: "Ignore performance" by r00t · · Score: 1

      Sure, many businesses are mismanaged.

      Lots of us do care about power. We fill racks with at least two VIA chips per 1U slot. Errr... VIA isn't made by AMD. Well, good luck to them!

    2. Re:Translation: "Ignore performance" by drdanny_orig · · Score: 1
      ...most people purchasing server technology probably won't care about power consumption. It's not their budget being wasted on power, it's some other overhead account they don't have access to.
      You have no idea what you're talking about. Power consumption is right up there with performance and footprint/rackspace in customer concerns. And the savings can be quite significant. It's a prime reason AMD is still in business.
      --
      .nosig
    3. Re:Translation: "Ignore performance" by Gr8Apes · · Score: 1

      In single threaded apps, I think AMD will at least be equal to Core 2 with their 65nm K8L architecture.

      In the server realm, Intel's a has-been. Their market share's falling faster than a rock through air. If you need proof, check out who all announced AMD powered servers recently (HP, IBM, Sun, and even Dell).

      As for the quad performance numbers, I think Intel's going to wilt when AMD's quads come out and are tested against multi-threaded benchmarks.

      --
      The cesspool just got a check and balance.
  7. Who wants to guess by BlueBiker · · Score: 1

    what the usage graph will look like on actual consumer machines with typical currently available software?

    I'm betting that 99% of the time when the user's running some CPU-intensive application it'll look exactly like the image in TFA: One core busy with a single-threaded app, one core slightly occupied with background system tasks, and the other two cores twiddling their thumbs with nothing at all to do.

    Sure will be nice when we have more software that can make use of two or more cores!

    1. Re:Who wants to guess by Wdomburg · · Score: 1

      That might be true for desktops, but in the server space we can keep multiple cores fed nicely, thank you very much. :)

  8. Hardware outrunning software by BlueBiker · · Score: 1
    For my entire career (since 1983), hardware has outrun software, and OS software in particular.
    Seriously. How many years after the introduction of the 386 did we have to wait for a real 32-bit OS? [QEMM didn't count.] And Win95 was still largely based on 16-bit code.
    1. Re:Hardware outrunning software by Nutria · · Score: 0
      How many years after the introduction of the 386 did we have to wait for a real 32-bit OS?

      Zero.

      32-bit Unix had been running on the VAX & MC 68000 for years. Porting it to the AT platform was trivial.

      Oh, wait, did you mean Windows? But you said real OS.

      --
      "I don't know, therefore Aliens" Wafflebox1
  9. Amazing by Urtica+dioica · · Score: 2, Funny

    ...they are still letting people in on what some of the new features will be.

    A company announcing upcoming features in order to create hype for their product? Who'd have thought of that.

    1. Re:Amazing by Anonymous Coward · · Score: 0

      Well at least the features don't disappear before the product gets released... (hint: vista)

  10. Biggest way for AMD to save power by Aaron+England · · Score: 4, Insightful

    is to reduce the distance between their transistors from 90nm to 65. Intel started shipping their 65nm chips nearly a year ago (OCT 2005), while AMD has yet to ship any. AMD isn't expected to be fully converted to the 65nm process until mid-2007, and by then Intel is expected to start shipping their 45nm chips. AMD is playing catch-up these days and it's hurting them bad.

    1. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 1

      Then again AMD does not have the nearly unlimited resources for FABs that Intel seems to have. While Intel is reaping the power benefits of its new 65nm tech, AMD released the "low power" versions of its X2 lineup, which are lower power than even C2D; hinting that maybe AMD's new 65nm processors (which will appear late this year/early Q1 '07) might be pushing 30-50W TDP for its desktop parts. Imagine what AMD could do for mobile if they have the ability to lower their mobile wattage to ~15-20W TDP for a Turion X2? Might finally be able to give CD a run for its money in the battery dept.

    2. Re:Biggest way for AMD to save power by marcosdumay · · Score: 1

      That, of course, if you ignore current leaks...

    3. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 0
      until mid-2007, and by then Intel is expected to start shipping their 45nm chips

      And... Who is expecting such an imaginative thing?

    4. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 2, Interesting

      Intel have publically stated that they will not be shipping 45nm chips until 2008.

      Intel shipped a few 65nm processors in 2005, but didn't really get started until 2006, and full conversion might not have happened yet, although all the important plants should have migrated by now.

      AMD have been behind on the process node, but that's not the only issue when it comes to making chips, although it is the most major. SS + SOI are other technologies that AMD is far ahead of Intel on, and they help reduce power significantly - hence AMD's low power 90nm processors compared to Intel's 90nm, and even Intel's 65nm P4s, and AMD aren't doing too badly in terms of performance/Watt right now either.

    5. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 1, Interesting

      Thank you, Intel marketing department!

    6. Re:Biggest way for AMD to save power by Aaron+England · · Score: 4, Informative
      Intel have publically stated that they will not be shipping 45nm chips until 2008.

      Nah. Here's what Intel's 45nm page says: This important milestone demonstrates that we are on track for 2007 to manufacture chips on 300mm wafers using the new 45nm (P1266) process, in accordance with Moore's Law.

      Intel shipped a few 65nm processors in 2005, but didn't really get started until 2006, and full conversion might not have happened yet, although all the important plants should have migrated by now.

      Even if true, AMD has yet to ship a SINGLE 65nm processor. By this measure alone, I'd say the claim that they are a year behind is quite adequete. But by the speed at which AMD is producing fab plants, I'd argue that they are or soon will be an entire chip generation behind.

      AMD have been behind on the process node, but that's not the only issue when it comes to making chips, although it is the most major. SS + SOI are other technologies that AMD is far ahead of Intel on, and they help reduce power significantly - hence AMD's low power 90nm processors compared to Intel's 90nm, and even Intel's 65nm P4s, and AMD aren't doing too badly in terms of performance/Watt right now either.

      Traditionally Intel has won the absolute performance title. As you said yourself it is the biggest factor when it comes to performance/Watt statistics. If been following any of the Core 2 Duo reviews, Intel is now dominating in that arena too.

    7. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 1, Insightful

      Alright, this annoys me a little. AMD has always been "playing catch-up". That's what they do to stay ahead. It's strange, I know, but it makes sense. They let the other guy go first, and then follow in the tracks close behind.
      AMD has always just sat back and studied Intel's moves, and then acted accordingly. Basically, their stratagy is to take the technology that the others had a year ago, and use it much better.
      This is why they've had lower MHz ratings, but equal or higher performance than Intel. This is why they have had DDR running neck and neck with DDR2 for so long with little to no performance hit.
      They wait for the technology to mature and then apply it correctly.

      Don't get me wrong, Intel has a place, they make great chips. Some one has to go first, and they do some things better. But then again, AMD does some things better than Intel, too.

      Sorry, I just don't like hearing fanboy-ism.

    8. Re:Biggest way for AMD to save power by Gr8Apes · · Score: 1

      They're behind? Until Intel's just released Core 2 chips, Intel was a generation behind. AMD will be releasing their next gen in about 6-9 months. Intel's next gen won't be out for a long while. Don't forget, Core 2 is a fallback to the old P-III/M architecture utilizing a shared cache. It's Intel's Plan B, and they're still scrambling. Furthermore, initial tests on Woodcrest indicate that Intel's already hit the FSB wall with a mere 2P system.

      AMD will be utilizing a shared L3 cache on their next CPUs, don't suffer from FSB issues, and are pretty effectively infinitely scalable in number of processors (and cores, for that matter). I'd say Intel's toast. I'll give them their last hurrah for these 6-9 months though. Core 2 has the crown.

      --
      The cesspool just got a check and balance.
    9. Re:Biggest way for AMD to save power by Anonymous Coward · · Score: 0

      Actually the Core 2 is nothing like the Pentium 3/M. It is a totally new architecture with macro ops fusion and wider execution units and branching units. Your just an AMD fan boy that needs to get your facts straight. AMD gets to play follow the leader and make a second copy of everything Intel does. Where does it say the front side bus has hit a wall? You could at least provide something to support such a useless opinion. The Front Side bus can be scaled upwards in bandwidth and megahurtz and number of buses and bit width. It has not hit a front wall. You can add 4+ or increase the width or speed from 1000 megahurtz to 1333 megahurtz or higher and have 4 of them or even increase the bit width from 64 to 256 ect. A bus is just a bus.

      AMD's claim about the memory controller is a bunch of crap. At least with Intel you don't have to upgrade the processor to bump up memory in the memory controller like the AM2 with DDR. The memory controller can be upgraded in Intel chips since it is decoupled unlike AMD trash. Also the Sun t1 has 4 memory controllers to the AMDs 1.

      Traditionally Intel has had a lot of cache in there chips. The argument about a level 3 cache is garbage too. Intel can add a level 3 cache as well. Intel's chip's should be able to scale just as well as AMD's. AMD's process tech is nowhere near what Intel's is.

    10. Re:Biggest way for AMD to save power by Calinous · · Score: 1

      Shared L2 cache is good, as long as you can keep its latency down (as Intel did). The reason - one core can have to do a task that is limited in memory access (and uses just a bit of cache), while the other core can use all the rest of the L2 cache. As for the post I replied to, yes, Core2 is a totally new microarchitecture - derived from Intel Core, derived from Intel Pentium Mobile, which was started from the Pentium Pro/P3 architectures. This is, it has more in common with P3 than the Netburst/P4. Widening the FSB could be difficult - you must double the number of traces that carry a signal very vulnerable to delays. Increasing the frequency might be possible - running now on 266MHz signals, quad pumped (1033), and overclockers were able to get at the 500MHz - let's say you could double the FSB at most. As for the AMD and memory controller, how many times would have you upgraded the memory without upgrading the processor? And how many times would the usual customer do so? (I did changed the memory in my mainboard from SDR to DDR once - but for the next change, I will buy a new mainboard/processor). As for Sun and its 4 memory controllers - I suppose you want to refer to AMD's server processors, the Opteron, where each processor can have its own memory. Niagara has four memory controllers? Four Opteron cores have four memory controllers too.

    11. Re:Biggest way for AMD to save power by Gr8Apes · · Score: 1

      You're just an Intel fanboy. (Wow, that was fun, now that the name-calling's done, let's get down to real discussion)

      Let's tackle your FSB assertion first. Woodcrest shares a FSB between 2 CPUs. To state that they can scale just by increasing the bus clock is the same argument used for the now thoroughly discredited P4. You can't keep increasing FSB without making trade-offs that will usually run into one wall or the other (heat or interference are the 2 main ones for FSB speed)

      When did Intel get NUMA? That's pretty much what's required for CPUs to have their own FSB and still work together. (If you're only looking for virtualization type systems, this isn't important.)

      The Sun T1 has 8 threads. Using 4 memory controllers is probably a good thing. I think you're confused with Intel chips. AMD chips have 1 controller per core. As for upgrading, when's the last time you upgraded a memory controller? Heck, when's the last time the memory controller was a problem in an AMD system?

      Intel has double the cache, because that's the only way they can even be in the ballpark, until recently with the Core 2. As for L3, Intel dropped L3 because it was too expensive. Anything can be done, it's merely a question of cost. As for process tech, Intel's got 65nm right now, AMD competed with them on 90nm because of superior tech - SOI. When AMD hits 65nm, and Intel goes 45nm, I think you'll find AMD's performance will still be neck and neck at best for Intel. Why @ best? Because Intel's got nothing else up their sleeve.

      --
      The cesspool just got a check and balance.
  11. it's better actually by r00t · · Score: 3, Informative

    AMD now provides a TSC (cycle counter) that doesn't vary in speed when the core speed changes. This greatly helps with timekeeping.

    As for race conditions: that is pretty well taken care of already. SGI has Linux on a 2048-way system now.

    1. Re:it's better actually by gmack · · Score: 2, Interesting

      But were the 2048 way systems running at different clock speeds? Or rather were the processors in each node running at different clock speeds? Last time I saw someone on linux-kernel mismatch processors it brought all sorts of interesting issues out.

    2. Re:it's better actually by Jah-Wren+Ryel · · Score: 2, Informative

      But were the 2048 way systems running at different clock speeds?

      Different clock speeds should not present much of a problem. In terms of performance it should be a non-issue - right now you can get variable performance out of the same code depending on other factors like memory contention, cache pollution by other processes, etc so if a cycle takes 1.00ns or 0.50ns isn't going to be anything new.

      Only the scheduler is going to care about frequency differences, and considering that we already have the ability to dynamically vary frequency on current systems (intel speedstep, amd's cool-and-quiet) presumably the scheduler already knows how to handle variations in clock frequency - it probably uses a counter/interrupt-generator that is not affected by varying the clock.

      Last time I saw someone on linux-kernel mismatch processors it brought all sorts of interesting issues out.

      I'm going to guess that by "mismatch processors" there was more to it than just clock frequency. Probably at least cache size and type, maybe TLB size, and probably a bunch of similar minutae too. It's likely the kernel makes some assumptions about those kinds of characteristics, but they aren't likely to vary on the new AMD chips in the way they could with different models of chips in the same system.

      --
      When information is power, privacy is freedom.
  12. Re:Irony by Anonymous Coward · · Score: 0

    It's "Yes, it's like 'goldy' and 'bronzy' only it's made out of iron.". If you're going to borrow lines from Blackadder to such bad effect, at least get them /right/.

  13. Power is always key by bblboy54 · · Score: 5, Informative

    Well, at least if you are in a data center.

    There are two huge concerns in a typical data center enviornment: Heat and Power. These two areas are key because of the density of servers today. We're cramming so much processing and storage into 48U that people 10 years ago couldnt have even dreamed of even existing. Delivering enough power to run 48 servers can be difficult if each server is pulling 4 amps each (thats 192 amps). Considering most circuits are 20 or 30amps, thats alot of circuits to fit in one rack.

    This was always the biggest reason why Dell servers were not as popular with the companies that I have worked with. Quite simply, AMD was kicking Intel's ass with heat and power. I heard many people say they'd start ordering Dell servers by the pallet if they sold AMD processors (looks like they finally listened).

    1. Re:Power is always key by Anonymous Coward · · Score: 1, Informative

      You're not kidding...

      Imagine a freezer -- AC units so efficient that they can form ice in a room 200'x200'. Think so cold that you need to wear a jacket or else you start getting blue in the lips. Now imagine baking a typical Thanksgiving turkey... Remember how how it gets in front of the oven when you pull out the turkey? Well, that's what our datacenter is like. Since populating the rest of a blade server unit, the area behind the units feels like sitting in front of that oven. There's a 60 degree Fahrenheit temperature difference between the air going in and the air coming out.

    2. Re:Power is always key by Anonymous Coward · · Score: 0

      Ya, but how many 1U servers are actually pulling 4 amps? I think your numbers are a little high.

  14. I don't get the point of this by Sloppy · · Score: 3, Interesting

    I'm sceptical that this technique will be very useful. (Of course, AMD is full of smart people and I'm just some net.moron.) I don't think it will be very common for the load on a 4-core processor to be somewhere the middle like 1.5. It's either going to be mostly idle (load close to 0) so you might as well power down the whole chip, or going full blast with the load as high as I think will give me the most throughput. For example, when compiling (and that's when I wish I had more cores) I'm gonna "make -j n" and my load is going to be about n, and that number is going to be chosen to be one more than the number of cores I have (or something like that). If I have a 4-core machine, do you think I'm going to make -j 2? No way.

    I can't think of many situations where I would have one core running at 100% and another at 50% and the others idle, for any significant length of time. I can imagine a desktop user clicking on something and maybe for a few milliseconds that load is somewhere around that, but then the work gets done and you're idling again. Or the user asked it to do something "hard" so all cores are near 100% (except maybe while waiting for I/O) for a "long" time.

    Am I wrong? What kinds of things does your computer work on, which are a little parallelizable but not very much?

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    1. Re:I don't get the point of this by Anonymous Coward · · Score: 0

      In a server environment, like I am in, most applications are still not threaded. They are single tasks that get scheduled to systems based on their availabilty, system speed and task priority.
      It is very often that you will have one process screaming at 100% of a core, one doing a lot of io using only 75% of a core and two cores doing nothing, waiting on the next task for them to do.

      Obviously the correct solution is to thread everything to the point where we have n+1 threads running on a box where the threads spend some time in IO, and n threads running when the jobs tend to be CPU intensive.

      This is actually something we have spent a good deal of talking about recently, and ultimately, when there is a large volume of work to do, sometimes load is the last thing you need to look at, but cpu% iowait and paging is more important. One trick I had used in the past with compiles, is doing a make -j n+1 (because of all the IO involved in a kernel compile.)

      Efficiently using multiple cores with single threaded applications (and eventually a hybrid of single and multi-threaded applications) is an important area for us right now. I think the first goal we have is to raise the average User cpu% on the systems, then look at reducing iowait% then tackle nfs wait (which I am still trying to find a good way to track under the 2.6 kernel).

    2. Re:I don't get the point of this by Mr.+Hankey · · Score: 3, Interesting

      One of my computers (well, 'one' and 'my' being relative terms in this case) is a 40 node cluster, completely SMP with some of the newer nodes being dual core as well. Often they're fully utilized or more, imagine a 5.00+ loadavg per node weeks on end. When a job is winding down though, the remainder of the jobs will probably finish up one at a time and you often have a few CPUs with just one job running for a few days. It's good for the electric bill to allow the CPU cores to power down.

      Another of my computers is basically used to play games. Most games don't seem to do much on the SMP side, so I doubt it would much matter how many cores there were as far as the game's concerned. They do tend to peak one CPU pretty much all the time though, while another core might end up servicing OS calls. Again, it couldn't hurt to let those sleeping processors/cores power down while they're not doing much of anything.

      --
      GPL: Free as in will
    3. Re:I don't get the point of this by tomstdenis · · Score: 1

      Um? are you kiddin? I have a 2P 285 box [dual core 2.6Ghz] and in certain applications [e.g. video encoding] only a single core is used [damn you mencoder!!!]. Why would I clock up the other cores? Now cpufreqd does clock down the other PROCESSOR but the other core on the same processor as the mencoder process is clocked up.

      You are right that in certain high load applications you may not need it. But remember for every live server in the world there are dozens of test boxes which take power just the same. Those test boxes RARELY have anywhere close to 100% load and could benefit greatly.

      Instead of making two processors, one which can idle and one which can't, you might as well just make one that can idle.

      Tom

      --
      Someday, I'll have a real sig.
    4. Re:I don't get the point of this by Jeremi · · Score: 2, Interesting
      Am I wrong? What kinds of things does your computer work on, which are a little parallelizable but not very much?


      How about games and media playback? In those applications, you have X amount of work that needs to be done every (say) 33ms... there might be more work to do than one core can handle, but not so much that you need all 4 cores.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    5. Re:I don't get the point of this by Alkivar · · Score: 2, Interesting

      Games.... at least for the moment. Very few companies producing games are parallelizing their code. I can see the 100% being the core the game is running on, and the 50% core being the overhead of the interaction between the CPU an GPU. At least thats the only scenario I can currently think of...

    6. Re:I don't get the point of this by Wdomburg · · Score: 1

      Think servers, not desktops. They're going to be the target for both the processing power of four cores and the adaptive power features AMD describes.

      Just looking at one of our web clusters, we vary from ~ 150 to ~ 3500 requests per second, with fairly smooth build-up. Certainly not all or nothing.

    7. Re:I don't get the point of this by Jeff+DeMaagd · · Score: 1

      I think generally cores 2-4 can probably be turned off or put to sleep most of the time. I have a dual processor system and only rarely do I see a need to have the second processor on at all.

      For games, I can see core one doing the graphics and core two doing I/O, system overhead, network and audio. Cores 3 & 4 can probably go to sleep unless they are doing some video transcoding or something like that.

    8. Re:I don't get the point of this by Bobsledboy · · Score: 1

      If the video encoder you're using doesn't use all 4 cores, you need to change your video encoder.

    9. Re:I don't get the point of this by tomstdenis · · Score: 1

      Why? It encodes a single pass at ~60fps, it's free software, it does a very good job with libavcodec of making mpeg4:ac3 movies, etc.

      I was encoding three movies at a time for a while. All hitting ~50fps per pass [25fps overall]. Good enough for me. Oh, yeah I guess I could pay for [or steal] a commercial encoder. But since I only have to encode my DVD once, it doesn't really matter.

      Tom

      --
      Someday, I'll have a real sig.
    10. Re:I don't get the point of this by Ant+P. · · Score: 1

      Sound processing. Simulating 50 or so sound effects in a 3D environment without a high-end sound card with hardware OpenAL takes a huge amount of CPU time.

  15. OpenGL equivalent for Ray Tracing by ErroneousBee · · Score: 2, Interesting

    How does this tally with a previous story about multi-core architectures being ideal for realtime ray-tracing in games? Is anyone working on a Ray-Tracing evuivalent of OpenGL?

    --
    **TODO** Steal someone elses sig.
    1. Re:OpenGL equivalent for Ray Tracing by Anonymous Coward · · Score: 1, Interesting

      As a game developer and developing 3D engines, I looked into this issue circa 1999. Using Moore's Law (albeit very wrongly) to have twice the computing power every 18-24 months, I calculated Ray Tracing would become feasible in real time (@640x480 - 1024x768 resolution) in about 28 years (back then).

      I haven't really contemplated it lately, but I still figure we are about ~20 years off. Of course, graphics cards have really advanced in the meantime, picking up the slack from CPUs whose acceleration in pure speed seems to have peaked between 1997-2004 (bell curve).

    2. Re:OpenGL equivalent for Ray Tracing by Anonymous Coward · · Score: 0

      Rather than speculating wildly, why don't you perform a web search and check out some real-time raytracing demos? These run very slowly in DOSBox (1-3FPS), but some have windows executables that work quickly in WINE.

    3. Re:OpenGL equivalent for Ray Tracing by Anonymous Coward · · Score: 0
      Rather than speculating wildly


      What part of "I calculated" escapes you? I would look at those Raytracing demos with more interest if I had not made a few myself. But they aren't perfect for predicting everything unless you are willing to make a game out of it. Many demos just have their 1/2/3/4/5 objects in a relatively small confined box - hardly the same condition as most games.
    4. Re:OpenGL equivalent for Ray Tracing by Lord+Crc · · Score: 1

      Is anyone working on a Ray-Tracing evuivalent of OpenGL?

      Actually, yes: OpenRT. Some games which uses it can be found here, although nothing you can try at home unfortunately, only videos available for download.

    5. Re:OpenGL equivalent for Ray Tracing by Anonymous Coward · · Score: 0

      Apple is apparently developing a multithreaded version of OpenGL. Does that count?

  16. not me by Anonymous Coward · · Score: 0

    AMD and Intel are last century. bor-ing! I am looking forward to some cheaper mobos that have both POWER and CELL onboard. That's my idea of "dual". *IBM* is where cutting edge happens.

  17. Microthreading to the rescue. by Majik+Sheff · · Score: 1

    This was one of the marvels of the BeOS. It excelled at one thing above all else: Multithreading. Almost every part of an application was a lightweight thread, and the kernel's scheduler was a work of art. It's really a shame that the original architects never got a chance to finish their "sticky threads" impelmentation; cache trashing was a real bottleneck on heavily loaded machines.

    --
    Women are like electronics: you don't know how damaged they are until you try to turn them on.
  18. Efficiency, yes by grammar+fascist · · Score: 4, Funny

    AMD Says Power Efficiency Still Key

    I'll be happy with these new processors as long as I can still efficiently heat my apartment with them.

    --
    I got my Linux laptop at System76.
    1. Re:Efficiency, yes by Anonymous Coward · · Score: 3, Interesting

      I'm afraid that I'm being a thermodynamics fascist, but you really can't efficiently heat your apartment with CPUs. Typically, for every BTU of heat delivered to you by electrical power, 2 more BTUs go up the power station smokestack or are lost in transmission. In contrast, for every BTU delivered from a modern gas furnace, less than 0.1 BTU goes up the chimney.

    2. Re:Efficiency, yes by Sabre0591 · · Score: 2, Funny

      You've got that right. I heat my spare room with a pair of 64bit AMDs running in two desktop units. Now if I can just figure out where to put the other four maybe I can shut down the furnace this winter.

      --
      The manual said "install Windows XP or better", So I went with Linux.
    3. Re:Efficiency, yes by Anonymous Coward · · Score: 0

      Ah, but what about delivery of gas to furnace, and other such factors?

    4. Re:Efficiency, yes by Anonymous Coward · · Score: 0

      For this example we'll assume that the residential gas delivery overhead is roughly equivalent to that of delivering gas, coal, etc. to the central power station, so it cancels out.

    5. Re:Efficiency, yes by jsoderba · · Score: 1

      And if we assume the moon is made of cheese, we can discuss what it tastes like.

      Building and maintaing a gas distribution network that covers every household requires vastly more energy than delivering the gas to a small number of power stations, especially given that there still needs to be an electricity grid either way. I'm not saying electric heating is as efficent as gas, but your figures are certainly exagerated by a wide margin.

      You say that all the waste heat is lost at the power station, but at least here in Finland, many power stations distribute their waste heat to near-by homes and industries. From a conservationist viewpoint, replacing the fossil-fuel-powered power station with cleaner power sources is much easier than replacing a gas burner in every home.

    6. Re:Efficiency, yes by Anonymous Coward · · Score: 0
      Building and maintaing a gas distribution network that covers every household requires vastly more energy than delivering the gas to a small number of power stations

      Nonsense. Building offshore platforms and shipping the gas thousands of miles is the part that takes the vast majority of the resources. Sending it a few more miles to a house is nothing.

      I'm not saying electric heating is as efficent as gas, but your figures are certainly exagerated by a wide margin.
      Oh yeah? Prove it. Most power stations are significantly less than 50% efficient, and transmission losses compound that. Very few power stations utilize much of their waste heat, as most of them are too large to have enough customers close enough by to make use of it. Most modern furnaces are > 90% efficient. Sure, a heat pump would change that equation, but a CPU is a resistive heater, not a heat pump.
    7. Re:Efficiency, yes by IHC+Navistar · · Score: 0

      The hell you can't heat an apartment with a CPU. I get, and keep, my room at a comfy 75 degrees even (at least it feels like that, even with the window open. Shorts, no shirt, no shoes...no problem.). Running a Tyan motherboard with dual AMD Opteron 246 CPU's (only one of which is currently installed), an ATI 9800PRO All-In-Wonder graphics card, and a 500W PSU in an open case. I know, I SHOULDN'T be letting them run like that, but when my system is running 24/7, the heat it cranks out will keep it toasty, even if it is, literally, freezing outside. More still, a buddy of mine had a graphic arts class in high school where the room was at around 80-85 degrees because of all the rendering they were doing. They would have to run the AC in the WINTER just to make class somewhat bearable.

      Yes, *YOU CAN* do it, but it will take a little longer, obviously, than a gas-fired or electrically-fired furnace. Some of us were just geeky enough to do it. Belive me. I can.

      Anyone who says you can't heat a room or apartment with a CPU is using an abacus.

      -----

      Sig Sauer

      --
      Knowing Google's lust for data collection, the Soviet Union is still alive and well inside the psyche of Sergey Brin....
    8. Re:Efficiency, yes by Anonymous Coward · · Score: 0

      I didn't say that you can't do it. I said that you can't do it *efficiently*. I.e., without consuming more overall fuel than just using a good furnace.

    9. Re:Efficiency, yes by popsicle67 · · Score: 1

      Yeah I've seen some of the tech you Finns use and I gotta say that Americans have lost the ingenuity race for sheer cool factor. We should start throwing brains at our problems instead of just making more money to buy more energy. I still wonder when a genius engineer will figure out how to put a refrigerator and a cookstove together so we can combine those two heat cycles into one. My ex-inlaws just got done having a home built with some technology from swedish builders(not surprising as mom-in-law is just one generation removed from people that spoke more old country than english and 2 gens from people that didn't know america except for pictures)and the floor does 3 jobs instead of one. It is a concrete slab 18 inches thick with a series of tubes patterned through it and it acts like a giant sump for heat now and the temp inside is a steady 75 with summer raging into the high 90's here. In the winter,hot water gets circulated through the tubes to warm the floor and the house. They tested that part while the interior was still empty and the windows were just plastic sheeting and you had everything from pleasant and comfy up to "christ it's hot in here" without any other heat source. Finally it also supports the usual foot traffic, but except for an occasional touchup on the sealer every ten years or so they'll never have to worry about wear and tear. The roof has an offset peak with windows facing away from the prevailing wind so no hot stale air trapped at the ceiling either. The coolest thing though is the boiler for hot water. They had to go electric because the location was impossible for an installed gas line and delivery trucks tend to be a pain in the ass for a tank setup but the hot water system is compact and instead of saving up a big bottle of 120 degree water for needs it has a superheated reservoir with a cold premix stage for delivery and the reheat rate is so good that you never get a temperature drop the way you do with a standard water heater. My ex and her sister are already doing rock paper scissors to see who gets the place when the parents kick off but their great grandma lasted till 102 and her mom was around for almost that long so they have a wait ahead of them

  19. Better move back to... by Anonymous Coward · · Score: 0

    Windows NT 4.0 and run it on a multicore MIPS or PowerPC based CPU.

  20. Re:Look at AMD's malfeasance! by NihilEst · · Score: 1
    You're kidding, right?

    Compared to everybody else on the list (see Intel), AMD looks pretty clean.

    --
    Founding member: He-Man Windoze Hater Club
  21. they already do that.. by YesIAmAScript · · Score: 1

    AMD already can halt the two cores in an X2 setup independently.

    This saves power, but better yet would be if you could (halt and) power down the cores independently. AMD cannot do this yet, but Intel can.

    --
    http://lkml.org/lkml/2005/8/20/95
  22. you don't want to do that... by YesIAmAScript · · Score: 2, Insightful

    I didn't know AMD could do that, as I run Windows and under Windows the two cores speed up and slow down (several steps from 1GHz to 2.2GHz) at the same time.

    But you don't want to do it anyway. If you look at the voltages to the cores, as the cores slow down, the voltage goes down too. This reduces power used and also reduces leakage (which is large at 90nm and can be large at 65nm). The problem is that both cores receive the same voltage, so you can't reduce the voltage to the one core that is slowing down unless the other one slows down too.

    So you'd rather run two cores at 1.7GHz and 1.2V instead of one core at 2.4GHz and 1.4V and one core at 1GHz and 1.4V. The power usage goes down with the square of the voltage, so the former case is saving 25% more power than the latter.

    --
    http://lkml.org/lkml/2005/8/20/95
    1. Re:you don't want to do that... by undeaf · · Score: 2, Interesting

      Okay then. So that means that you can't just shift most of the power to one CPU to make it much more efficient at single threaded tasks, but also that it still should be quite beneficial to run multiple cores at different speeds.

      Assuming that each core is like an individual CPU, odds are, one core is better than the other. That would mean that for both cores to run at the same speed, the better one would have to be getting more voltage than it requires, or be running slower than it could be(those two things are basically equivalent). So the optimal solution would be to link the state of the cores, but for each state, set each CPU to the maximum it can go at that particular voltage.

    2. Re:you don't want to do that... by Vlad_the_Inhaler · · Score: 1

      I didn't know AMD could do that, as I run Windows and under Windows the two cores speed up and slow down (several steps from 1GHz to 2.2GHz) at the same time.
      At the moment, AMD can't - this capability will be new. The more cores a processor has, the more you need this independent control.

      I imagine this sort of capability will mean a lot to companies running large server farms - think of Gooogle. I don't think I will need a 4-core machine at home, although a 2-core which runs CoolnQuiet independently (will they backport this capability?) *would* be nice.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
  23. Point taken by BlueBiker · · Score: 1

    You're right about Unix/Xenix having long existed in both 32-bit and 16-bit. I was just referring to the long delay between the debut of the 386 in 1986 and OS/2 2.0 in 1992 and WinNT in 1993.

  24. Coolness Counts by Doc+Ruby · · Score: 1

    Power efficiency was the reason cited by Apple for dumping IBM/PowerPC for x86. If AMD can clean Intel's clock with coolness, I wonder how long until Apples are Intel's biggest competition again.

    --

    --
    make install -not war

  25. Power isn't the only criterion by BlueBiker · · Score: 3, Insightful
    So you'd rather run two cores at 1.7GHz and 1.2V instead of one core at 2.4GHz and 1.4V and one core at 1GHz and 1.4V.
    If you have a single thread going flat out, you'll be sacrificing performance if you throttle its core down to achieve voltage parity with a second mostly idle core. Instead of having idle cores drag the speeds down, maybe active cores should push the speeds up.
    1. Re:Power isn't the only criterion by Wesley+Felter · · Score: 2, Interesting

      Instead of having idle cores drag the speeds down, maybe active cores should push the speeds up.

      Exactly. Intel calls this EPI throttling in one of their recent papers.

  26. Re:Look at AMD's malfeasance! by Anonymous Coward · · Score: 0

    no, he's merely trolling for page hits, as you can see from here: http://slashdot.org/~applix7

  27. AMD has always been a half-step behind in process by WoTG · · Score: 1

    I doubt that AMD has launched a new process within 6 months of Intel in the last decade. It's a almost a basic fact of life. Intel has the money and experience to manufacture at smaller dimensions sooner than AMD. Sometimes 6 months, this time about a year.

    It's not necessarily "hurting them [AMD] bad" though. The Opterons are still quite competitive in power use versus the latest Core 2's (certainly not as bad as the P4 vs the Opteron). Plus, there are time and cost benefits to letting Intel work out the kinks in the system -- obviously Intel doesn't tell AMD what to do, but there are changes that affect shared suppliers that benefit everyone.

  28. I'm sick of marketing by suv4x4 · · Score: 1

    Modern companies believe the features of their products are merely an excuse for their marketing campaign statements. Like with HD DVD / Blue Ray.

    Speed is apparently no longer something you need to care about: all CPU's are about fast enough for most uses.
    Cores... I swear a modern OS (Vista including) can simply make no use of more than 2 cores.
    Power efficiency: they are all more or less the same, unless you have a Pentium4 / Celeron (P4 based) on a laptop/desktop system, in which case you may upgrade.

    64-bit -> that's the last selling point. And AMD offers this for a long time now. Intel will sell plenty of Core 2-s since they are late on the train.

    But then what? They should either invent totally new way to use a CPU or scale down dramatically (both AMD and Intel).

    1. Re:I'm sick of marketing by Jesus_666 · · Score: 1

      Cores... I swear a modern OS (Vista including) can simply make no use of more than 2 cores.

      Then you use two OSes. Sure, the market of people who run Linux and Windows simultaneously so they have one OS for gaming and one for everything else is small but that's just one possible application.

      For most home users more than two cores ain't that great, but for certain powerusers and for professional IT (think "servers") it might be interesting, especially with things like per-core power management.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    2. Re:I'm sick of marketing by Anonymous Coward · · Score: 0

      I don't buy that speed is useless. I run simulations at work that max out a CPU for a week. I play games that are CPU-limited when it comes to adding more enemies or increasing the resolution. Most importantly, I use a 600 Mhz laptop - the difference between that and a modern desktop is like night and day, and I can imagine that moving to a 6Ghz desktop processor would also make a big difference. Sure, some things will remain limited by hard drive speed, but even that can be worked around with compression, and hard drive read speed can be sped up with RAID striping.

      I think you're on the money with dual core being the sweet spot though. Speed can go up forever, but more than 2 cores is going to result in a lot of idle time for numbers 3 and 4.

      64 bit is only truly useful (as opposed to just being a slightly faster processor, more registers, blah blah) to people who want lots of RAM, and who don't use 32-bit windows. So for almost everyone who's bought it, it's not actually a selling point. Weird...

  29. AMD Says Power Efficiency Still Key by suv4x4 · · Score: 1

    "AMD Says Power Efficiency Still Key" .. funny, I thought customers tell to vendors what is key. When did this turn the other way around?

    1. Re:AMD Says Power Efficiency Still Key by Phil+John · · Score: 2, Informative

      Customers are wanting better power efficiency. Due to the rising costs of energy a lot of data centres are now charging based on energy consumption and heat output (needs more AC -> needs more energy). It's becoming a real problem, especially for some data centres who for varying reasons cannot increase their electricity supplies. That's why google, microsoft and others have started building data centres near a hydro-electric dam in the states, cheap and plentiful electricity.

      --
      I am NaN
  30. Interesting, how does that work out? by Lonewolf666 · · Score: 1

    I know that the individual VIA CPU does not need much power, but it is also significantly weaker in performance than an AMD or Core 2 Duo dual-core.
    So how many VIAs do you need to replace one AMD or Intel?

    --
    C - the footgun of programming languages
    1. Re:Interesting, how does that work out? by r00t · · Score: 1

      The task I'm thinking of is not number crunching, so it works out.

      (start an app, wait until the app is fully started and idle, examine the app and OS state, kill the app, repeat)

      Remember the cost of air conditioning too.

    2. Re:Interesting, how does that work out? by WuphonsReach · · Score: 1

      A rough guideline is that a 600MHz VIA C3 (fanless) is about half the processing power of a Celeron 566MHz (Pentium III core). That's based on personal experience and not anything scientific.

      OTOH, that little VIA C3 system on my shelf draws a miniscule amount of power (including the 2 laptop HDDs). Makes a very good firewall PC for my home network.

      (Yes, I know about the Linksys router that runs Linux. No, I don't own one. I had the VIA C3 sitting around from a previous project.)

      --
      Wolde you bothe eate your cake, and have your cake?
  31. Hyperthreads competed for execution units by BlueBiker · · Score: 1

    AIUI, a scheduling challenge with hyperthreading was ensuring that two simultaneous threads didn't compete for the same types of execution units [int or fp or vector?] at the same time. That wouldn't be a problem with separate cores, each with their own execution units.

  32. X2-3800+ (ADD) has performance/Watt crown by edxwelch · · Score: 2, Informative

    Actually the new low power X2-3800+ (ADD) now has the performance/Watt crown.
    It has idle power of 8 watts and full load of 25 watts.
    They measured the performance of various benchmarks and also the energy required to perform the benchmark to get a figure for performance/Watt and the
    X2-3800+ came out miles ahead of the Conroe (or any other chip). http://www.lostcircuits.com/cpu/low_e/6.shtml

  33. When did this turn the other way around? by argent · · Score: 1

    When it started to cost more for the electricity to power a server for a year than it cost for the server.