Slashdot Mirror


What Makes Apple's Power Mac G5 Processor So Hot

An anonymous reader writes "58 million transistors can drive a lot of power. Apparently, Apple appreciated the choices IBM processor architects made when designing the 970 family. This article provides the 64-bit architecture big picture for the 970 family (A.K.A. the Power Mac G5) and the critical issues in IBM's 64-bit POWER designs, covering 32-bit compatibility, power management, and processor bus design."

83 of 313 comments (clear)

  1. Circular Logic by WormholeFiend · · Score: 4, Funny

    If it's so hot, maybe it's not cool enough.

  2. What Makes Apple's Power Mac G5 Processor So Hot? by Anonymous Coward · · Score: 5, Funny

    Insufficient cooling?

  3. What makes it so hot (abridged) by Sensible+Clod · · Score: 3, Insightful

    Basically, we took one of our superchips that go into superservers, with a gitastic cache and frontside bus, stripped it down a bit so we don't cut into our own market, and gave it a new name. Isn't that cool?

    --

    The difference between spam and poop is that you don't have to dig through septic tanks looking for real food. -- Me
    1. Re:What makes it so hot (abridged) by malfunct · · Score: 4, Interesting

      Its not that apples (and most likely some of the x86 based computers too though I haven't really looked into it) aren't supercomputers. Its just that given the current definition of a supercomputer its just not that amazing anymore. Maybe its the definition that needs to change rather than you being upset at people that follow the definition.

      --

      "You can now flame me, I am full of love,"

    2. Re:What makes it so hot (abridged) by John+Whitley · · Score: 5, Insightful
      Wow. Artful and elegant rebalancing of engineering tradeoffs for very diferent markets reduced to a knee-jerk oversimplification in one fell swoop. And it got a +5 Insightful for that, too boot. Here are some reasons why the "stripped it down a bit so we don't cut into our own market" statement is ridiculous:
      1. If selling POWER series chips to Apple was going to undermine IBM's server business, IBM would have a hell of a lot more to worry about from the plain 'ol x86 market.
      2. IBM's POWER-series chips are designed to trade away ultra-high-speed clock rates in favor of low failure rates. The design rule (feature size on chip) is pulled back from the bleeding edge and other layout techniques are employed to make these processors rock solid, to avoid costly downtime from hardware failures in business servers.
      3. These days Apple is well known for its forays into the cluster computing space -- but that's a far cry from the sort of transactional throughput capacity of IBM's high-end servers. I.e. not the same markets!
  4. 64 bit integers by Xpilot · · Score: 4, Insightful
    From the article:
    ...64-bit processors also accelerate complex mathematical calculations through their ability to perform calculations directly on 64-bit numbers...
    Don't they mean 64-bit integers? Since floating point registers in most modern CPU's are 64-bit wide already.

    --
    "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
    1. Re:64 bit integers by francisew · · Score: 5, Informative

      More importantly, it doesn't have to break the 64 bit operations into many successive 32 bit operations. 64 bit operation are not simply 2x32 bit operations, but can be several dozen operations.

      An 8-bit microcontroller can perform 64 bit floating point operations correctly. It just takes a long time.

    2. Re:64 bit integers by Waffle+Iron · · Score: 5, Informative
      Since floating point registers in most modern CPU's are 64-bit wide already.

      Actually, since most modern CPUs are x86 variants, the floating point registers are usually 80 bits wide (and have been since the 1981 introduction of the 8087).

      As far as "complex mathematical calculations" go, 64-bit integers aren't really that big a deal. It's pretty rare to need integers bigger than 2^32 but no bigger than 2^64; floating point usually handles big numbers more flexibly.

      The big deal with 64-bit CPUs is 64-bit address pointers and operations on them (which usually aren't more complex than adding and shifting).

    3. Re:64 bit integers by cimetmc · · Score: 2, Informative

      Sorry, but you are completely wrong here.
      A lot of 32 bit processors already have a 64 bit data bus right now. This is for example the case for the Intel 32 bit processors. So loading an entity bigger than 32 bit is not an issue. The bus width between the processor core and the L1 cache is even wider allowing even bigger chunks to be loaded in one cycle.
      As for the floating point unit, it is also designed to do the operations in double precision (64bit) or even more. Once again, full 64 bit processors have no advantage here.
      So for floating point numbers, having a full 64 bit processor compared to current 32 bit processors does not give you any speed advantage. The only advantage that remaines is the bigger address range.

      Marcel

    4. Re:64 bit integers by Fulcrum+of+Evil · · Score: 2, Informative

      A lot of 32 bit processors already have a 64 bit data bus right now. This is for example the case for the Intel 32 bit processors. So loading an entity bigger than 32 bit is not an issue.

      This is not relevant to the instruction stream - you still need two load instructions. Actual bus widths are not visible to executing code - it's simply there to improve bandwidth.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    5. Re:64 bit integers by dgatwood · · Score: 3, Informative
      Pentium 4 has eight 32-bit general-purpose registers. The G5 has 32.

      You're right that P4 has a lot of rename registers, but those aren't directly accessible. Thus, their usefulness is limited by the CPU's look-ahead. In theory, a compiler can always do better if it has access to the same number of registers because it can look arbitrarily far ahead.

      Oh, but you were trolling. You didn't actually expect an answer, did you? Well, you got one.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  5. Re:anyone else noticed how COOL the AMD-64 chips r by Noah+Adler · · Score: 5, Insightful

    I was able to hold my hand on the heatsink and it was barely warm.

    It could be because there's inadequate conduction between the CPU core and the heatsink. Check the temperature monitors to make sure it's actually as cool as you hope it to be. It could be that just most of the heat is staying in on the CPU, which would be a bad thing. Hopefully you've already checked this though.

  6. ob Memory by GillBates0 · · Score: 4, Funny
    18 exabytes ought to be enough for anybody

    -GillBates0, 2004.

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
    1. Re:ob Memory by Mark_in_Brazil · · Score: 5, Informative
      18 exabytes ought to be enough for anybody

      -GillBates0, 2004
      So where does it end?

      This page makes a fairly convincing argument that 256 bit CPUs should be enough (basically, there would be no way to exhaust the amount of memory a 256 bit CPU could access, because the number of memory locations is about the same as the number of atoms in the universe).

      --Mark
      --
      "It is nice to know that the computer understands the problem. But I would like to understand it too." --Eugene Wigner
    2. Re:ob Memory by brsmith4 · · Score: 2, Informative

      Dude, that's insane. You'd have to build a ram stick with more mass than the entire universe to exhaust the memory addressing capability of a 256 bit chip.

      All i can say is "Whoa".

    3. Re:ob Memory by PureCreditor · · Score: 2, Funny

      Umm....what about addressing subatomic particles ? =)

  7. Re:What Makes Apple's Power Mac G5 Processor So Ho by sky289hawk1 · · Score: 4, Funny

    The fan belt on its search engine doesn't drive the radiation air emission unit fast enough! SHE NEEDS MORE POWER!

  8. Teflon underside by suso · · Score: 4, Funny

    They should make the G5 powerbooks have a teflon underside.

    "Turn it over, and you can cook dinner".

    1. Re:Teflon underside by 21chrisp · · Score: 2, Funny

      My old OC'd PIII doubles as a space heater.

    2. Re:Teflon underside by suso · · Score: 2, Informative

      No kidding. Recently we moved two of our computers from our house office into another real office. The average temperature of the upstairs floor dropped 3 degrees F. It was amazing how much heat those were generating from the CPUs and hard drives.

    3. Re:Teflon underside by Reducer2001 · · Score: 4, Funny

      Ah ha! The REAL cause of global warming. OC'd CPU's.

      --
      When you get to hell -- tell 'em Itchy sent ya!
    4. Re:Teflon underside by NathanBullock · · Score: 3, Funny

      Imagine the problems trying to type while your laptop keeps sliding around on your lop.

    5. Re:Teflon underside by sp00 · · Score: 2, Funny

      Why turn it over? Just make a heatsink cooker like this guy did.

  9. Increased Pointer size by trigeek · · Score: 5, Interesting

    One side-effect of 64-bit computing that I don't hear a lot of discussion about is the increase in the size of a pointer. A standard implementation of a linked list of integers will now be 50 to 100% larger (depending on if you use 32 or 64 bit integers), simply because the pointers take up more space. If I bought a 64 bit system, simply because it's the "Best", but only got 1GB of RAM, I have less useful memory, because the pointers take up all of my physical RAM. Do the architects of these systems take this into account?

    --
    Sometimes I doubt your committment to SparkleMotion!
    1. Re:Increased Pointer size by Eccles · · Score: 4, Insightful

      In most meaningful, sizeable programs, pointers aren't a significant chunk of memory usage. (And for small programs, it doesn't matter.) I would think most modern apps consume most of their memory storing images, which aren't affected by the 32->64 change.

      Also, 64-bit pointers allow you to go from a max of 4GB of RAM to 16 billion GB, so the assumption is memory prices will keep dropping and you'll have much more than twice as much RAM on your 64-bit system anyway.

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    2. Re:Increased Pointer size by Myolp · · Score: 3, Funny

      After reading the privous post, I somehow got to think about viagra spam... "Increase The Size Of Your Pointer Now! Buy A 64-Bit PowerMac G5 And Get That Extra Size Today!"

    3. Re:Increased Pointer size by zulux · · Score: 2, Informative

      A linked list is just a container, so yes, if you're using your linked list - pointers will eat a bunch of space if you're storing small bits of data.

      But then again, you don't have to use linked lists. The C++ standard template library has all sorts of wonderful containers that may be better suited than simple linked-lists. Java has some neat containers as well.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    4. Re:Increased Pointer size by HeghmoH · · Score: 4, Interesting

      On Mac OS X, dynamic memory has a granularity of 16 bytes. That means that if your linked list node is only 8 bytes (4 bytes data, 4 bytes pointer) then it will get a 16-byte allocation anyway, and you'll waste the extra space. Using 16 bytes per node won't hurt at all. Allocation overhead makes the standard linked list a fairly wasteful way to store data anyway.

      --
      Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    5. Re:Increased Pointer size by 21chrisp · · Score: 2, Insightful

      Since the AMD64 instruction set can also run code compiled for 32 bit, it can also work with 32 bit pointers. However, any code optimized for AMD64, will probably contain all 64 bit pointers.

      I guess if you plan on shelving out for 64 bit, you should plan on getting more ram w/ it.

    6. Re:Increased Pointer size by tomstdenis · · Score: 2, Informative

      It wouldn't be safe to assume a pointer can be stored in 32-bits in 64-bit mode. The OS can map your data anywhere in the 64-bit space [which maps physically to a 40-bit bus, at least on my AMD64]. It's also not portable to do that. Even if your OS maps stuff within 4GB [e.g. top 32-bits are zero] another 64-bit box [sparc, ppc, etc..] may not [and likely would not] do that.

      If you build in 32-bit mode [e.g. -m32] you lose the major benefits of the 64 which is namely the extra registers.

      Tom

      --
      Someday, I'll have a real sig.
    7. Re:Increased Pointer size by lisaparratt · · Score: 2, Interesting

      On Silicon Graphics 64-bit machines, this was solved by having two ABIs, one 32-bit, one 64-bit. You could still use 64-bit operations in either mode, but pointer size depended on the width of the ABI. This allowed you to optimise memory use on small memory jobs, but still have access to vast amounts of RAM when you had to, just by choosing the right ABI for the job.

    8. Re:Increased Pointer size by Anonymous Coward · · Score: 3, Interesting

      This is an excellent observation. Please forgive me if this seems offtopic -- my primary development platform is PC, however I've got quite a bit of experience working on 64 bit.

      From a developer perspective (at least in software I've worked on) programmers often do not realize that a vast number of projects took dependencies on 4 byte pointers.

      Structure alignment, pointer size, etc have plagued all projects I've worked on, even after a cursory perusal at the code indicating "It looks good". Lots of bugs in porting code to 64 bit can be hidden until the right things happen.

      Your particular example probably overexaggerates the point (I doubt many modern apps use a majority of memory in integer linked lists). When you think of standard server apps, most data is serialized request data which is a significant constant overhead. For the average desktop user, typing documents & email is their primary utilization of a PC, in which case it shouldn't have a tremendous effect.

      That being said, there is no way your memory usage will become more effecient :-).

      One additional reason that your memory will drop -- on 64 bit platforms compiled binaries become much larger. This plagues the IA64 chipset more than any other -- due to their "four simultaneous operations" (forgive me if I'm misrepresenting -- this is only through hallway chatter) binaries get an order of 2 to 4 times larger (mostly full of NOPs, no less).

    9. Re:Increased Pointer size by spaceyhackerlady · · Score: 4, Informative
      On Silicon Graphics 64-bit machines, this was solved by having two ABIs, one 32-bit, one 64-bit.

      Sun machines with UltraSPARC processors do this too. They run 64 bit kernels, and applications are 32 bits. Unless you actually need 64 bits, in which case you feed the compiler some differnet options and it makes a 64 bit executable for you.

      Both Solaris and Linux do it the same way. When you build a kernel for Linux on an UltraSPARC machine the part about kernel support for different kinds of executables offers you (among other options) 32 bit ELF (which you need), 64 bit ELF (optional), and Solaris emulation (never tried it...).

      ...laura

    10. Re:Increased Pointer size by SnapShot · · Score: 5, Funny

      The C++ standard template library uses MAGIC PIXIE DUST and MOONBEAMS for the data structures. Java Containers, on the other hand, are held together with PURE THOUGHTS and KITTEN WHISKERS. That's how they avoid using pointers... ;-)

      --
      Waltz, nymph, for quick jigs vex Bud.
    11. Re:Increased Pointer size by fitten · · Score: 2, Interesting

      This probably depends on the compiler (and compiler flags). This is an optimization by the compiler to match memory allocation to cache line length for better performance. If you look, you'll find compiler options to allocate on whatever boundary you want.

      Otherwise, it would just be a design of the memory allocation libraries (always allocate on 16-byte boundary) for similar reasons (and to lessen memory fragmentation).

      Still good information to know about Mac OSX.

    12. Re:Increased Pointer size by bar-agent · · Score: 2, Funny

      As an aside, did you know that Java has garbage-collection as a side-effect of using pure thoughts to hold its data structures together? And the kitten whiskers are what allows the JIT compiler to work so well.

      On the other side of the fence, C++'s usage of magic pixie dust and moonbeams is what gives it its flexibility -- and by that I mean the ability to program in the procedural style or object-oriented style or template style, etc. The downside is that magic and moonbeams aren't really...reliable. So you end up shooting yourself in the foot, and every compiler is different.

      --
      i'd hit it so hard, if you pulled me out you'd be the king of britain [bash.org]
    13. Re:Increased Pointer size by aphor · · Score: 2, Informative
      I would think most modern apps consume most of their memory storing images, which aren't affected by the 32->64 change.

      You may forget that a bitblit, or a bulk memory copy operation can be accomplished in half of the time using the same number of 64 bit registers as 32 bit registers. How do you think common operations like scaling and color transformation will be affected by the increased register size and memory IO path? In my experience (Ultrasparc real world apps like GIMP and OpenSSL) most bulk integer compute operations complete in 10-20% less time when run in 64 bit mode vs 32 bit mode on the same computer (probably potentiated by L1-L2 cache performance differences in each mode), and they consistently consume about 1/2 the userland CPU cycles during that time. The biggest payout in 64 bit computing I have found is using OpenSSL with the 64 bit assembly code for encryption routines and having the 'bn' (big number) math library in 64 bit mode: I could scp database dumps across the network at full speed without dipping into enough cpu cycles to affect normal operation.

      --
      --- Nothing clever here: move along now...
  10. Re:Heat Problem Back Ground by jrockway · · Score: 5, Interesting

    I'll probably get modded down for saying this, but I have Karma to burn...

    That article is some crybaby whining about how expensive the G5s are. "Apple is so dumb. Why would anyone pay that much for a CRAP computer," is what the article sounds like. I think that guy needs to take his superior knowledge elsewhere and try some benchmarks ("512K of cache isn't competitive for $3000")... apparently it is because it's winning benchmarks and people are buying them. Just because you can't afford it doesn't mean it's a bad computer (doesn't mean it's a good computer either). This guy needs to grow up and write an article with facts instead of emotions...

    --
    My other car is first.
  11. The Athlon64 is very cool by Compact+Dick · · Score: 2, Interesting


    I recently upgraded to a 754-pin Athlon64 3000+, and the hottest it's ever been is 51 C, a few degrees more than the room temperature of 43C. On a cooler night, with 100% CPU load for ~2.5 hours [2-pass XviD encoding], it peaked at 47 C. Quite impressive.

    1. Re:The Athlon64 is very cool by strictfoo · · Score: 4, Funny

      Holy fuck dude... your room temp is 109.4 degrees Fahrenheit (thank you google)?

      Open a window or buy an air conditioner or something!

      --
      I've just signed legislation that'll outlaw Russia forever. We'll begin bombing in five minutes.
    2. Re:The Athlon64 is very cool by Your+Pal+Dave · · Score: 2, Funny
      a few degrees more than the room temperature of 43C


      Holy Crap! You must be really roductive !
    3. Re:The Athlon64 is very cool by Compact+Dick · · Score: 3, Funny
      Holy Crap! You must be really roductive !
      And if you were to move to my place, spelling errors would decline! ;-)

      Cheers!

      -- CD

    4. Re:The Athlon64 is very cool by RangerElf · · Score: 3, Informative

      You live in the Kalahari desert?

      He might live in Tucson or Phoenix, Arizona; the Sonora-Arizona desert is quite a hot place in summer. Around Hermosillo, Sonora, there's a permanent high-pressure system which pushes off any clouds coming our way, so there's uninterrupted sunlight some ... 14 hours a day :-)

      All through July and August, the normal, everyday noon-time temperature is over 45 C, 47 C is not really all that surprising. Once I was out in the street at 50 C.

      Being a desert, it cools down quickly at nighttime; but when there's no breeze to take away the heat, it sucks evilly to be at 10 PM and still at thirty-something C. So, being at 43 at night is awful. I know how you feel though.

      The best part is the faces others make when they find out about summer in Hermosillo: "But, that's impossible!" Naa, just a bit warm.

      -gus

    5. Re:The Athlon64 is very cool by sigaar · · Score: 2, Interesting

      In some parts in the world it does actually get that hot. Ever been to Africa? How is 32C on an avarage winter's afternoon for you? Now just imagine the summer...

      Anyways, I've ony ever touched an Athlon64 once. It was a 3000+ and ran 28C at idle. Granted, room temperature was 25C (office aircon). Don't know what it would do in a hotter room.

      Room temperature can make an enormous difference. My PC at home is a 2400+ AthlonXP, which ran at about 45C all winter under full load - room temperature is cold, below 15C. Now with summer approaching, it's already in the 50s. Guess I'll have to invest in a proper Thermaltake or something...

      --
      sigaar
    6. Re:The Athlon64 is very cool by Fulcrum+of+Evil · · Score: 2

      Ever been to Africa? How is 32C on an avarage winter's afternoon for you?

      Which part? Africa has pretty much every environment present on the planet (possibly excluding tundra). If Ghana is 32C in December, I'd expect it to be about 34C in July.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  12. Addressing by vlad_petric · · Score: 4, Informative

    Most importantly, it can address up 2^64 bytes of memory. And yes, that generally implies 64-bit integer GPRS. BTW, vector operations on x86 (MMX) also operate with 64 bit registers, but it can only access 4G (32G if you use the extended bits "hack").

    --

    The Raven

    1. Re:Addressing by javax · · Score: 2, Informative

      The classic IA32 (aka x86) only has 32Bit for addressing memory (w/o using any evil hacks).
      AA64 (aka AMD64/EMT64) uses an incompatible new addressing mode to use 64Bit pointers (though it can operate in 32Bit compatibility mode, too)

  13. WATT figures for G5 vs AMD-64? by green+pizza · · Score: 4, Interesting

    Does anyone have the numbers to compare how many watts of power the G5 uses vs a similar AthlonXP or AMD64? Ie, I'd like to see how a 2.0 or 2.5 GHz G5 compares to a 2.0 or 2.5 GHz AMD processor.

    1. Re:WATT figures for G5 vs AMD-64? by hattig · · Score: 3, Informative

      Apart from the 2.6GHz FX55, but that is a top of the line 130nm part, the best of a process generation. And some people are overclocking these on air to 2.8, 2.9GHz. I expect that the FX55 uses around 100W though, because it isn't a 90nm part and it is the fastest

      AMD's 90nm 3500+ uses under 67W of power however at 2.2GHz.

    2. Re:WATT figures for G5 vs AMD-64? by Anonymous Coward · · Score: 5, Informative

      It's hard to make a comparison because for some reason IBM/Apple doesn't want to release official measurements for power usage. Which is strange because they should do really well in that measurement compared to AMD and Intel. Here's their official numbers:

      2.4 GHz A64- 89 W
      3.4 GHz P4(Northwood)- 89 W
      3.4 GHz P4(Prescott)- 103 W

      Best guess on the 2.5 GHz G5 is around 65 W.

    3. Re:WATT figures for G5 vs AMD-64? by nelsonal · · Score: 2, Interesting

      First off power consumption for a processor = .5*C*V^2*F where c is capacitance, V is voltage, and F is frequency. So if you can find capacitance you can get a pretty good estimate of the processor's power needs.
      From Intel's datasheets: P4 90 nm (prescott) 520-550 models 84 W of design power (what Intel recommends the heatsink be able to pull).
      550-560 models 115 W of design power.

      From AMD's datasheets: design power (measured with max amplitude and nominal voltage) is 89 watts for all power ratings 3000+ to 3700+.

      I couldn't find a PPC 970 data sheet at IBM but ee times claims it pulls 97 watts, but speed was not specified. That seems consistent with the water cooling on the G5, my air cooled P4 is plenty loud.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
  14. Nitpicking... by Tristandh · · Score: 5, Insightful

    Capable of addressing an astronomical 18 billion GB, or 18 exabytes, of memory,

    I know the first 2 digits are 1 and 8, but 2^64 bytes is still 'only' 16 exabytes...

    1. Re:Nitpicking... by TonyZahn · · Score: 4, Informative

      If you had read the sidebar you'd see the article defined the issues with base-2 and base-10 number names, and introduced the prefixes "mibi-" and "gibi", which should be familiar to /.ers.

      When they say 18 exabytes, they're talking base-10, otherwise they would have used the "gibi-" equivalent (exibytes?)

      --
      - sig? who is this sig of which you speak?
    2. Re:Nitpicking... by Fulcrum+of+Evil · · Score: 2, Insightful

      When they say 18 exabytes, they're talking base-10, otherwise they would have used the "gibi-" equivalent (exibytes?)

      If they meant base10, they should have used existing conventions (10^x) rather than trying to shoehorn this kibi stuff into usage. Common usage is that an exabyte is 2^60 bytes. Nobody in there right mind uses exibyte for that. The standard is something that NIST is trying to force on the community without any sort of support - they're exceeding their mandate.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  15. Re:So sick of it by BobWeiner · · Score: 4, Funny

    Obligatory PC Weenies link that fits the topic at hand.

    --
    The PC Weenies: 11 Years of Online Tech 'Too
  16. Re:Heat Problem Back Ground by the_2nd_coming · · Score: 5, Insightful

    umm, what heat problem? the 9 fans and liquid cooling are in their respective models to solve a SOUND problem. not a heat problem. but then if you bothered looking up statistics on the G5 you would not be able to bash the mac would you?

    --



    I am the Alpha and the Omega-3
  17. Add instruction sets size too by Gopal.V · · Score: 3, Interesting
    The instruction sets are also generally 64 bit... so you end up with lesser disk space as well :) .. add the space in loading these into RAM ..

    The notable exception is the Arm's thumb instruction set (it's cool).

    The sad part "my address bus is bigger than you" is going the "I have more MHz than you" way soon as parallel CPUs (mulit-core or otherwise) become cheaper.. 90% of our tasks are better done parallel than using a single fast chip . Hell , half of the tasks really don't need anything beyond a 300/400 mhz clocks.
    1. Re:Add instruction sets size too by taradfong · · Score: 2, Informative

      IA64 (Itanium) has 64 bit instructions, *but* each can hold up to 3 opcodes.

      --
      Does it hurt to hear them lying? Was this the only world you had?
    2. Re:Add instruction sets size too by ArbitraryConstant · · Score: 2, Informative

      In the case of PowerPC (and SPARC, MIPS, anything else I can think of), the opcodes is still 32 bits. The number of registers stays the same, the number of instructions stays (more or less) the same. There is no reason to extend the size of opcodes.

      --
      I rarely criticize things I don't care about.
  18. Re:you want heat data by Anonymous Coward · · Score: 3, Interesting

    The power coming out of a chip is marginal; it's pretty much all converted to heat.

  19. PC vs Mac cooling. by coobachey · · Score: 2, Funny

    In the past few years where PC' Fanatics have gone to great measures in extreme clocking and tweaking to push the speeds to the limits, Mod'rs have ran into and pretty much conquered heat issues along with other roadblocks. Technology that has been adapted by PC and PC-part manufacturers, I'm no Mac expert but even thumbing through the latest magazines I have yet to stumble upon a "Mac" mod or a how-to on making them extreme, is this due to proprietary or licensing issues? Or can a Mac be reverse engineered the way PC's can be? Granted Macs are not worthless and have good reviews from most of its users that know the systems. Still I find it limiting and where PC has prevailed. Heat on a slower clock speed processor should not be an issue. How many fans does a G3, G4, G5 have these days (1 case)? Laptops would be even worse as for PC portables are highly concerned about heat themselves.

    "Make it idiot proof, Someone will make a better idiot" -- Tweak

    Coob

  20. Fans and cooling by 2nd+Post! · · Score: 5, Interesting

    Your iMac G5 has two fans. Not much space left for additional cooling, really, without interfering with the current cooling setup.

    Your PowerMac G5 has nine fans. Again, not much space left for additional cooling without interfering.

    And get this, the PowerMac G5 already uses a liquid cooling setup. The only possible additional mod is to hook the current setup to a resevoir and radiator on the outside of the case, as the inside already has a radiator per CPU and something like a 120mm fan per CPU.

  21. I doubt that 64 bit computing is that hot for PPC by renoX · · Score: 3, Insightful

    The *BIG* thing for x86 for "64bit computing" is not in fact the 64 bitness but doubling the number of GPR!

    As the PPC instruction set is sane (x86 is not, urgh), beside the extra-instruction needed for 64 bit computing, there are very few difference between a PPC running on 64bit code or a PPC running on 32bit unless of course you have an app which needs more than 4GB of memory or do lots of 64-bit integer calculation..

  22. Re:Nice title... by Anonymous Coward · · Score: 2, Interesting

    It's not a matter of total heat dissapation as much as the fact that the head is dissapated in very small areas of an allready tiny chip.

    The PPC970FX actually doesn't produce that much heat compared to the current AMD and Intel crop, only dissapating 54W typical at 2.5Ghz (albiet a good deal higher at peak). But due to it's smaller die, it has to dissapate that heat from a smaller area, thus requiring a cooler heat sink to dissapate it into to maintain the same die temperature.

    It's basic thermodynamics, but something geeks often overlook.

  23. Re:So sick of it by Lumpy · · Score: 2, Insightful

    I can buy .8-1.2ghz processors and motherboards that use extremely little power (tens of watts running full bore) and are certianly very useable with even windows XP running on it as a internet/ general use home or office pc.

    But for some reason most people believe they need a 6.8ghz 2.2terabytes of ram and 15,000 rpm hard drives along with a hairdryer add on known as a 3d video card, bringing that machine up to the 400 watts+ power consumption mark.

    and where does most of that energy go?? that 's right . HEAT.

    Switch to mini-itx computer with a low-power processor, laptop hard drive and flat panel monitor, and you will generate very little heat, use 1/20th the electricity your current space heater under your desk called a comouter does and still get the same general computing done with the same speedy feel.

    will you increase your lead in the seti@home, doom3, other CPU intensive tasks? nope. but office 2003, WinXP and all other office apps as well as most non 3d intensive games run perfecly.

    --
    Do not look at laser with remaining good eye.
  24. Re:Heat Problem Back Ground by coolgeek · · Score: 2, Interesting

    The G5 2.5 dualie I just received puts out waaaaay more heat than any computer I've ever seen. I had to move it out from under my desk to the side to allow the heat to escape. It was much more than a foot warmer.

    --

    cat /dev/null >sig
  25. It used to be... by Balthisar · · Score: 2, Interesting

    It used to be that Mac fanatics would be proud about how little current the PPC used -- and consequently how little heat it gave off -- when compared with the Intel-style architecture. Guess we can't make that argument any more.

    Now that G5's are liquid cooled, it makes me wonder if a 2.5GHz G5 is *really* a 2.5GHz G5, or if it's an overclocked 1.8GHz chip. You know, overclockers really pump things up with cool liquid cooling stuff. What's the fastest a 2.5GHz G5 could run with a traditional cooling system, like a fan and heatsink?

    Oh, one more thing before I'm modded as a troll: my G4 PowerBook is my 8th Macintosh. What I'm asking is genuine curiosity.

    --
    --Jim (me)
    1. Re:It used to be... by dhovis · · Score: 3, Informative

      I have mod points, but I figured I'd answer your question instead.

      When you do a die shrink, you can lower the power required at particular clock rate, or you can run at a higher clock speed with the same power dissipated. So when IBM went from 130nm for the 970 to 90nm for the 970FX, the top clock speed went up from 2GHz to 2.5GHz. Other than the process change, I believe there were very few changes to the chip.

      Now, when you go from 130 nm to 90nm, the linear dimension across the chip is ~70% of what is was, and the area of the chip is (70%)^2 or about 50% of the previous chip.

      Lets use some numbers, these may not be 100% accurate, but they'll explain the basic concept. The 2GHz 970 had a die size of about 121mm^2 and put out a maximum of 42W. That is about 350mW/mm^2. If we assume that the 2.5GHz 970FX has that same power consumption, but has a die size of 60mm^2, then the 970FX will produce 700mW/mm^2. So you have the same amount of power, but you are trying to suck it out of a smaller piece of silicon. So you need much more efficient cooling to keep the chip temperature the same. Hence, the liquid cooling system in the dual 2.5GHz G5.

      --

      --
      The internet is the greatest source of biased information in the history of mankind.

    2. Re:It used to be... by Balthisar · · Score: 2, Interesting

      I guess I should have been a little clearer. I know that the 2.5GHz chip is rated as 2.5GHz. I also know that just the clockspeed alone does not a system make. I realize the same amount of power has to be pumped through smaller pipes and be disapated. I realize it's quiet and I miss whisper-quietness of my graphite iMac (Mac #6).

      I guess the question I'm asking -- aside from being a question -- is really meant to be thought provoking. Does the use of a liquid cooling system fundamentally change the defacto cooling requirements for all future desktop computers? If you recall in the past, overclockers would use liquid cooling because they had to do so to keep the chip cool enough in order to increase the clock frequency. Higher frequency at this scale means more heat.

      How do chip manufacturers specify cooling requirements anyway? So many joules per second must be removed, or simply do they leave it open and say the chip must always be below x-degrees? So are IBM or Motorola marketing a chip that's not possible to be used in any other manner aside from liquid cooling? And in the most base form, couldn't Intel just re-badge a 3Ghz chip with ridiculous cooling requirements and advertise it as a 4GHz chip?

      Surely there must be something fundamental to the architecture of a chip (I don't know) that can account for its clockspeed (regardless of MIPS) aside from the ability to cool it, right? Well, up to reasonable frequency limits, right?

      --
      --Jim (me)
  26. Good followup link from the article by C.Batt · · Score: 5, Informative

    Introduction to 64-bit computing

    There's an informative link at the bottom of the article for those requiring a bit more insight into the effect of 64-bit computing. /wishes he had exa-bytes of memory right now... VS.NET on WinXP is a PIG!

    --
    -- All views expressed in this post are mine and do not
    -- reflect those of my employer or their clients
  27. Re:Nice title... by shotfeel · · Score: 3, Informative

    is there another reason to use liquid cooling, other than excessive temperature?

    Not sure if this is the reason, but its not just a matter of amount of heat generated. Its the amount of heat generated in a given area. So if you generate the same, or even less, heat in a smaller area, you may need to resort to something more efficient that air cooling to do the job.

  28. Re:Heat Problem Back Ground by WuphonsReach · · Score: 3, Insightful

    Just because you can't afford it doesn't mean it's a bad computer (doesn't mean it's a good computer either).

    Hear hear.

    I've priced out equivalent machines to the current Apple offerings, and you do indeed get what you pay for. A dual-CPU 1.8Ghz Powermac is around $2500 sans monitor. Price out a dual-Xeon or dual-Opteron and you end up at around $2000-$2500 for a comparable system.

    Where Apple might be missing the boat is in the ultra low end where you can buy a system for $600. (But why should they try to compete down there where margins are razor-thin?)

    --
    Wolde you bothe eate your cake, and have your cake?
  29. CPU power defeated by bloated software? by shed · · Score: 3, Insightful
    From the article:



    The quest for CPU power has been largely defeated by bloated software in applications and operating systems. Some programs I wrote in Basic on an Apple II ran faster than when written in a modern language on a G4 Dual-processor Mac with hardware 1,000 times faster.


    Come on. What language are we talking about here? My basement collection includes a II+, a IIe, two IIcs and a Franklin compatible. I challenge anyone to come up with a program in Applesoft that runs faster on one of my museum pieces than on a modern Mac using C++, Java or even Perl. I mod his article -1 for troll.


    While software has become bloated and to some extent inefficient, people often forget that we expect a lot more from our computers now than the single-tasking 80 column display days.

    --
    My cat can eat a whole watermelon
    1. Re:CPU power defeated by bloated software? by Tumbleweed · · Score: 2, Funny

      the single-tasking 80 column display days

      _80_ columns?! Why, you young punks had it good! When I was a boy, we only had 40 columns, and we felt grateful, as our fathers had no video display at all. Grandfathers? They used their fingers or an abacus.

      You've come a long way, baby.

  30. Re:Mac's are doomed! by repetty · · Score: 2, Insightful

    I agree, big time.

    I used to be very pleased that my Macs lacked a CPU fan while x86 users where bolting on everything but the kitchen sink in efforts to cool their systems down.

    More important, Macs had just one fan -- the power supply fan -- to cool the entire box while x86 systems were fucking festooned with them.

    Nowadays, though, a prudent Mac owner should at least consider his home air-conditioning system's cooling capacity since G4's and G5's will definitely heat up a room.

    And I don't even want to get into fan counts.

    I'd like Apple to make a nice, fast, cool, quiet system... and here's how to do it: underclock.

    Modern CPU's are grotesquely overpowered for the needs of 99.9% of the general public. Crank those babies back.

    The fruit of research and progress are not merely systems that can run faster and hotter, but faster and cooler... quieter.

    Never going happen while there's this pissing contest going on, though.

    --Richard

  31. Re:atoms in one universe by pclminion · · Score: 5, Funny
    So, what happens if you want to use your fancy computer to model two universes?

    Simple. Since we've got a computer capable of simulating the entire universe, we'll just use it to simulate a universe which contains a computer which is capable of simulating more than one universe.

  32. Re:Mac's are doomed! by GlassHeart · · Score: 2, Insightful
    It's not a pissing contest, by which I presume you mean a pointless pursuit. Apple was faced with an important market segment - audio and graphics professionals - jumping ship both because PC software are beginning to catch up and because PC hardware are not only cheaper but actually perform much better. For many of these customers, render time is money.

    If you don't need that kind of power, you should stay on the lower end. The G5 iMac or the eMac don't seem to run all that hot.

    As for fan count, presumably you're referring to the PowerMac G5. Apple preferred more low-speed fans over a few high-speed fans as a noise reduction measure. What was your complaint?

  33. Re:Heat Problem Back Ground by toddestan · · Score: 3, Insightful

    Where Apple might be missing the boat is in the ultra low end where you can buy a system for $600. (But why should they try to compete down there where margins are razor-thin?)

    Because poor college students like me, who buy $600 computers is going to buy a PC. And when I get out of college and have the means to drop $2500 on a computer, guess what I'll probably buy.

    Actually, the two real reasons why Apple doesn't sell low end machines is that it would undercut sales of their more expensive machines, and totally destroy the second hand Mac market (where used Macs are way overvalued, IMHO). Without a strong second hand market to sell a used Mac for a good price, people will be less likely to buy their high end machines.

  34. it's hot. really. (a little perspective) by Mr.+Slurpee · · Score: 4, Interesting

    for literal heat, this puppy is pretty hot.

    my dual 2.5GHz PowerMac G5 idles at 52C (125F) on CPU A and 50C (122F) on CPU B. the memory controller is actually one of the hotter things, it idles at 62C (143F). however, it's not the hottest thing, of course: at full load (DVD rip+encode or playing 15 videos at once + MP3 + tasks + flicking around Exposé) both CPUs have hit a max of 83C (181F) (the computer is supposed to automatically sleep around 90C or so).

    so why so effing hot? i mean, this idles at the max temp my athlon 2500 peaks at! it certainly idles at a hotter temp than it needs to, but i have no problem with that: the system runs the fans dynamically to keep the noise down, so at idle it's not as cool as it could be. the difference in noise in my room when i sleep the athlon is ridiculous - the G5 sounds like a slightly loud external hard drive that's spun up. the system also has a liquid cooling system to quench the processors. this seems to just keep the processors within their range. the value that i see in it is response to new heat - the CPU temps flick around a lot and are very responsive to load and the loss of load. after ramping up the CPUs to >80C, it take about three or four seconds after the load drops for the CPU temps to drop 15-20C, then maybe a total of ten or twelve seconds to drop to idle temp.

    for some real-world perspective... a DVD rip+encode with HandBrake with using ffmpeg engine, MP3 audio, 2-pass encoding, and gunning for your average 700MB movie time (800-1300kbps?) takes slightly less than the length of the DVD. an hour and a half long movie took about and hour and fifteen minutes to get on to my hard drive. MP3 ripping in iTunes will run up to 28x, but it's not fully loading the processors so i wonder about a drive read bottleneck. the first night i got it, i was at a loss for how to really test the speed on it, so i just decided to open up a shitload of videos. basically i played a DVD (fluff, the GPU does that), opened up something in VLC, opened up about 13 videos in QuickTime of various sizes and formats, played some MP3 music (fluff again, that's ball sweat of a cutting edge proc), and still had enough processing power to comfortably navigate files, chat, browse web pages, and flick around Exposé. around all of these things plus one is when a few of the videos would start stuttering and expose would start dropping frames to keep collapse speed uniform. anything past this would really start robbing time from videos.

    all in all? it's fast. it's quiet. it gets hot, but it takes care of itself. coming from a 375MHz G3-upgraded PowerMac 7600 (vintage '98), i'm not doing too shabby. i just decided i'd scramjet at mach 7 to the top of the pack and then sit there for another few years.

    --
    - emilio
    neurostyle dot net - it's all in your head
  35. Re: uh oh... by Cryptnotic · · Score: 2, Interesting

    What if our universe is only a simulation running on a computer in another universe?

    Maybe it's possible to disprove this based on the idea that the other universe would need to be physically larger?

    --
    My other first post is car post.
  36. Re: uh oh... by rekoil · · Score: 2, Funny

    That would go a long way to explain the "disappearing sock" phemonenon...

  37. It's the die size that requires additional cooling by willy_me · · Score: 2, Interesting

    They use liquid cooling because it's harder to disapate the heat from the small 90nm core. The CPU's don't use much power, it's just that the heat they do produce is concentrated in such a small area. Better cooling is required to disapate this heat.

    90nm transiters require less power then their larger counterparts. The problem is, for the same die size they use more power. So you end up with a relatively low power CPU that requires massive cooling.

    Apple and IBM had a lot of problems because they expected their new CPUs that consume less power to be easy to cool. They were wrong. For each square mm, more heat must be disapated.

  38. Re:Heat Problem Back Ground by jrockway · · Score: 3, Insightful

    But that's why people buy macs. To use photoshop quickly. So how long a filter application takes is very relevant.

    I don't have a mac here, but opterons and g5s are probably similar. Pick the one you like, they're both expensive :)

    --
    My other car is first.