Slashdot Mirror


Intel Turbo Boost vs. AMD Turbo Core Explained

An anonymous reader recommends a PC Authority article explaining the whys and wherefores of Intel Turbo Boost and AMD Turbo Core approaches to wringing more apparent performance out of multi-core CPUs. "Gordon Moore has a lot to answer for. His prediction in the now seminal 'Cramming more components onto integrated circuits' article from 1965 evolved into Intel's corporate philosophy and have driven the semiconductor industry forward for 45 years. This prediction was that the number of transistors on a CPU would double every 18 months and has driven CPU design into the realm of multicore. But the thing is, even now there are few applications that take full advantage of multicore processers. What this has led to is the rise of CPU technology designed to speed up single core performance when an application doesn't use the other cores. Intel's version of the technology is called Turbo Boost, while AMD's is called Turbo Core. This article neatly explains how these speed up your PC, and the difference between the two approaches. Interesting reading if you're choosing between Intel and AMD for your next build."

198 comments

  1. Can we get.. by vjlen · · Score: 5, Funny

    ...Turbo switches on our workstations again like back in the day?

    1. Re:Can we get.. by Bugamn · · Score: 1

      Oh, man, you tickled my nostalgia.

    2. Re:Can we get.. by sznupi · · Score: 4, Funny

      Plus a straightforward way of figuring out how to best assign processes to particular cores? (which ones are faster and which are slower)

      --
      One that hath name thou can not otter
    3. Re:Can we get.. by indre1 · · Score: 1, Insightful

      This seems like another marketing trick. I bet all the cores could easily run at the "super turbo boost" clock rates with an average heatsink and fan...

    4. Re:Can we get.. by Anonymous Coward · · Score: 0

      Back in the day??? What are you talking about??? Today I was using a computer at work that only had 640k of memory and a turbo button to go with it. Amazingly, 640k was enough for me to complete the task at hand, and I expect should be enough for everyone else.

    5. Re:Can we get.. by sznupi · · Score: 2, Insightful

      But perhaps not without exceeding the amperage value for which power lines are rated...

      --
      One that hath name thou can not otter
    6. Re:Can we get.. by Cryacin · · Score: 1

      I have a handle on the side of my laptop that I can crank to make it go faster.

      --
      Science advances one funeral at a time- Max Planck
    7. Re:Can we get.. by Anpheus · · Score: 3, Interesting

      Yes but it consumes more power and heat than they'd like. Binning is also a bigger deal than you think with CPUs. My CPU can be over-clocked significantly, because I got a lucky unit, but not nearly as much as what some people get. My CPU isn't stable at the memory speeds most over-clockers see online either. So in some ways, I got a good CPU, in some, it's meh.

      On the other hand, there's no way I'd sell a company my CPU & motherboard at the speed I've boosted it up to. Not a chance. It's not 100% stable, there are infrequent glitches, etc. I improved my cooling, decreased my over-clock, and I've still had it not wake up from s3 sleep and done a couple other odd things.

      So no, super turbo boost is not what you think it is. Is it a marketing ploy? Everything is a marketing ploy, but it's also a useful feature. Especially on laptops, where all but one core of the CPU can completely shut down and the remaining one can nearly double its clock speed.

    8. Re:Can we get.. by postbigbang · · Score: 4, Interesting

      So what you do is get people to code apps that use lighter-weight threads. Apple's GCD and FOSS ports of GCD spawn low-cost (as in overhead) threads so you can cram more in, make them smaller, and relieve part of the dirty cache memory problem in using them.

      Spawn threads across cores, keep thread life simpler. Make those freaking cores actually do something. It can be done. It's just that MacOS or Linux or BSD have to be used to run the app/games.

      Don't get me started on GPU threading.

      --
      ---- Teach Peace. It's Cheaper Than War.
    9. Re:Can we get.. by Anonymous Coward · · Score: 0

      We could, but that button is delivered as software now. For years actually.

    10. Re:Can we get.. by Anonymous Coward · · Score: 1, Funny

      Broke mine a while ago, now there's a vise-grip hanging off of one side. The real sad thing is using the original handle required less effort -- now when I come up from the basement sweating and panting with my laptop, the wife gives me funny looks.

    11. Re:Can we get.. by Anonymous Coward · · Score: 0

      I read the article, there's nothing about a math coprocessor being implemented so I highly doubt you'd see any marginal improvements in its performance if you switch turbo on ...

    12. Re:Can we get.. by larry+bagina · · Score: 1

      my netbook (eeepc) has a low power/high performance button.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    13. Re:Can we get.. by wealthychef · · Score: 2, Informative

      I like Grand Central Dispatch. Don't shoot me, it's from Apple. But it's open source, so it's good, right? What I like about it is that it relieves a programmer from the burden of choosing the number of threads to run, initializing all the various mutexes, etc. Very nice model. I don't see a big driver for adoption, unfortunately, outside of HPC geeks like yours truly.

      --
      Currently hooked on AMP
    14. Re:Can we get.. by Anpheus · · Score: 0

      Well that's all pretty obvious no? The only thing truly embarrassing about multicore is how poorly recognized embarrassingly parallel problems are.

      Microsoft supports lightweight threads (fibers), OpenCL runs on Windows, etc. The Go programming language, which runs lightweight threads in software, runs great on Windows. So, yeah, there are options for Windows. Saying that the only options are MacOS, *Nix and *BSD is pure FUD.

    15. Re:Can we get.. by DAldredge · · Score: 0

      If only Microsoft had things like that.

      http://msdn.microsoft.com/en-us/concurrency/default.aspx

    16. Re:Can we get.. by ckaminski · · Score: 3, Informative

      Last I checked, fibers were NOT useful for parallelism. They basically slave off of the thread that created them, and have to be cooperatively shared on that same thread of execution.

    17. Re:Can we get.. by hardwarefreak · · Score: 1

      ...Turbo switches on our workstations again like back in the day?

      Whadya mean 'back in the day'?

    18. Re:Can we get.. by electrosoccertux · · Score: 1

      heh, care to guess how many watts a CPU pulls?

      Now can you guess how many watts a wall outlet+power cable can give?

      Now compare those two....

    19. Re:Can we get.. by Hurricane78 · · Score: 5, Informative

      Actually, that’s pretty easy to do with Linux right now.
      Just choose any ACPI button (you at least have a power button, often more), and in your /etc/acpi/ directory, modify the scripts so they call “cpufreq-set -f $freq” on the right events. (You may need a state file in your /var/state/ dir, to remember which mode you are in. But you can also toggle a keyboard led that you don’t use much.)

      And this is why I love Linux. If you can think of it, and it’s physically possible... you can do it. :)

      Next: Using the graphics ram that is unused while in 2D mode, as a fast swap/tmpfs/cache. ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    20. Re:Can we get.. by Hurricane78 · · Score: 2, Interesting

      How about a small daemon that at intervals re-assigns the running processes to the cores in a balanced way (or one of your choice), and also sets the affinity for new processes. Should be about 30 minutes with any fast language of your choice that can call the appropriate commands.

      I think you could even do it with bash, although it would not be very resource-saving. (Hey, everything is a file even those settings! If not, then they did UNIX wrong. ;)

      Remember: You are using a computer. Not an appl(e)iance. You can automate whatever you wish yourselves. And usually pretty quickly too. :)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    21. Re:Can we get.. by Khyber · · Score: 1

      He's talking about PSU power rails, not mains power.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    22. Re:Can we get.. by Hurricane78 · · Score: 1

      Well, what I find very stupid, is that we programmers always preach modularity, but we still use mostly huge monolithic apps on the graphical desktop.

      I’d prefer the following:
      Imagine Photoshop. Or an office program. Now imagine everyone of those tools in the palette, buttons in the button bar, and menu items, becoming a completely separate program. With them all interacting trough a standardized interface, as an analogy to piping in shell scripting. And the property sidebars become the properties of those tools/wizards and of the document itself. Or actually also of any part (XML element, selection, etc) of the documents. Then you could just as easily use your Photoshop brush in your word processor or your word processing (or programmer’s editor) functionality to edit this very textarea that I’m typing in right now.

      And as a positive side-effect, if done right, multi-threading would not be an issue anymore.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    23. Re:Can we get.. by turtleAJ · · Score: 1

      ..and one Turbo switch per core!! =)

    24. Re:Can we get.. by grcumb · · Score: 4, Funny

      Plus a straightforward way of figuring out how to best assign processes to particular cores? (which ones are faster and which are slower)

      Heh, trick question. You almost got me there.

      You see, Intel stack their cores from fastest to slowest in order to maximise heat dissipation. This is known as a High-Endian architecture. AMD, on the other hand, use a Low-Endian architecture, stacking their cores from slowest to fastest because they claim it lowers power usage. So the real trick when trying to figure out which cores are faster is finding a cross-platform approach that won't penalise any given processor.

      The Slaughterhouse-5[*] method says that with a non-randomised Tralfamadorean transform, you can infer where your sample data is going to end up before you actually send it there. So you just measure the incipient idiopathic latency of your unsent bytes and then apply a parsimonious lectern to the results and voilà!

      ... Why, yes, I am in Marketing. Why do you ask?

      ------------------
      [*] As developed by Billy Pilgrim. Po tee-weet

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    25. Re:Can we get.. by beelsebob · · Score: 1

      You have it – assign the processes, and the cores they're assigned to will become fast. This doesn't need software fighting against it all the time.

    26. Re:Can we get.. by beelsebob · · Score: 2, Informative

      How about a small daemon that at intervals re-assigns the running processes to the cores in a balanced way (or one of your choice), and also sets the affinity for new processes. Should be about 30 minutes with any fast language of your choice that can call the appropriate commands.

      The linux scheduler doesn't do this? The OS X one certainly does, it also moves processes from core to core based on which one is getting hot.

    27. Re:Can we get.. by Anonymous Coward · · Score: 0

      Yeah it's soooo 80's, next they will be housed in red sports car body's with some blond washing the bonnet :)

    28. Re:Can we get.. by Anonymous Coward · · Score: 0

      I have a handle in my laptop that gets my day to go faster when I'm not busy, too.

    29. Re:Can we get.. by TheThiefMaster · · Score: 1

      The CPU pins, motherboard traces to them and the traces from them into the CPU proper are probably all narrower than the PSU wires.

    30. Re:Can we get.. by Anonymous Coward · · Score: 0

      Bullshit. Fibers do require manual scheduling (which for languages designed for parallelism is not a problem) but they are NOT tied to a single thread.

      From the documentation:

      You can call SwitchToFiber with the address of a fiber created by a different thread.

      BTW, this has been true ever since fibers were introduced. Maybe you didn't read the docs very carefully.

    31. Re:Can we get.. by L4t3r4lu5 · · Score: 1

      Please, PLEASE! I simply must buy a bridge!

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    32. Re:Can we get.. by Khyber · · Score: 1

      Guess why we prefer to use stranded wire instead of solid core for most power transmission?

      More surface area = more capability to carry power.

      The pins could probably all together support more power than the PSU power rails.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    33. Re:Can we get.. by electrosoccertux · · Score: 1

      No, he's not. At any rate people do that all the time, too no problems. Why? Because a 18g wire can carry a lot of DC current.

    34. Re:Can we get.. by atamido · · Score: 1

      Next: Using the graphics ram that is unused while in 2D mode, as a fast swap/tmpfs/cache. ;)

      That's a really interesting idea. Can that really be done?

    35. Re:Can we get.. by Simetrical · · Score: 1

      How about a small daemon that at intervals re-assigns the running processes to the cores in a balanced way (or one of your choice), and also sets the affinity for new processes.

      Yes, great idea. So that we don't have any idle CPU time, it would probably be best to run it every time any CPU core becomes available. That's pretty often, so actually, a daemon might not be a good idea; maybe it should be in the kernel instead. Now, what shall we call it? How about a "scheduler"?

      --
      MediaWiki developer, Total War Center sysadmin
    36. Re:Can we get.. by bjb · · Score: 1
      I think it was attempted in the past but didn't prove very useful.

      Two things to realize:

      1. The bandwidth of the graphics memory is extremely fast, but that doesn't mean it is fast to the rest of the system. I don't believe there is DMA to the entire video RAM on video cards (otherwise, your 1GB GDDR3 card would eat 1/3rd of your 32-bit OS's usable memory space). In other words, you have to pump it through some I/O window, I'd imagine.
      2. Flip the GPU into any 3D mode and there is the chance that it'll want to claim the memory your virtual disk is using. Considering Vista, Win7 and OS X do this to render their desktops, this might be a limitation.

      I don't claim to be an expert on this, but I remember thinking about the idea in the past and possibly seeing that someone tried and failed to come up with something useful.

      --
      Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
  2. Huh? by Wyatt+Earp · · Score: 5, Insightful

    That read like the pasting of two press releases together. That did very little to explain what is going on beyond press grade buzz words.

    1. Re:Huh? by Darkness404 · · Score: 5, Informative

      Essentially they both just detect if other cores can be powered down, power them down and then crank up the clock speed on the single cores because heat/power doesn't matter if the other cores are turned off or in the low megahertz. AMD's solution is like an afterthought because their architecture is older than Intel's while Intel's was built in to the architecture.

      --
      Taxation is legalized theft, no more, no less.
    2. Re:Huh? by Anonymous Coward · · Score: 0

      I think that's the point, it's meant to be a summary of the two approaches. if they're constantly referring to them in their various benchtesting articles it makes sense to have an explainer somewhere - i actually found it quite handy. the sort of assumed knowledge that would be handy in cpu/system reviews

    3. Re:Huh? by Wyatt+Earp · · Score: 1, Redundant

      The description said - "This article neatly explains how these speed up your PC, and the difference between the two approaches. Interesting reading if you're choosing between Intel and AMD for your next build."

      But it really don't have any performance information to help you choose.

    4. Re:Huh? by DeadboltX · · Score: 3, Informative

      The way I understand it (and I could be wrong) is that on a quad core 1.6ghz i7 each core is actually capable of going up to 2.8ghz, although I'm not sure if they are all capable of going to 2.8ghz at the same time. If you run a program that can't take advantage of more than 1 core, and it starts maxing out that core at 100%, the cpu will increase the clock speed of that core, up to 2.8ghz until it isn't maxed out anymore. In order to keep energy consumption and heat down the cpu will also lower the clock speeds of the other cores as needed.

      With older multi-core processors if you had a quad core 1.6ghz and you had a program that could only use 1 core then you would effectively just have a 1.6ghz processor, in which case a dual core 2.8ghz would be way better. With Turbo Boost you can essentially get the best of both worlds.

    5. Re:Huh? by K2tech · · Score: 0, Flamebait

      When will we stop referencing Moore's law? This has about as much relevancy today as Tom Watson's statement of "there is a world market for maybe five computers" made in 1943. Really, let it go. As a child I loved the TV show SPACE: 1999. But its gone now and not relevant, the same as Moore's law. No offense to the man himself, I truly do appreciate his work and discoveries. but it is time to move on. Say good night, Gracie.

    6. Re:Huh? by oldhack · · Score: 4, Insightful

      The damn thing could (and should) have been two-paragraph memo - reads like it's written by a high school kid trying to fill up page quota. Oh well - the info, as shallow as it is, still is something I didn't know before.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    7. Re:Huh? by gparent · · Score: 2

      Performance information?
      Intel is better.
      Has been that way for many years now. Yes, it's more expensive.

    8. Re:Huh? by Gr8Apes · · Score: 4, Informative

      Intel is better.
      Has been that way for many years now. Yes, it's more expensive.

      Depends on your metrics. If the only thing that matters is pure raw speed out of a single die, Intel does eek out on top, but not by as much as you'd think.

      If you're going for massive multi-processor, multi-core systems, it's AMD.

      If it's power vs performance out of a single die, then it depends - idle or full throttle. Intel for the former, AMD for the latter, depending upon weighting.

      and so on. At least as of the last set of performance benchmarks I read just a few months ago on the topic, meaning they're probably completely out of date by now.

      --
      The cesspool just got a check and balance.
    9. Re:Huh? by electrosoccertux · · Score: 1

      Essentially they both just detect if other cores can be powered down, power them down and then crank up the clock speed on the single cores because heat/power doesn't matter if the other cores are turned off or in the low megahertz. AMD's solution is like an afterthought because their architecture is older than Intel's while Intel's was built in to the architecture.

      It's actually existed since the original Phenom series of chips that came out a few years ago; and they've only recently given the BIOS code for it in these newer chips.

      On my Phenom 2 720BE (which I unlocked to a quad) I use Phenom MSR Tweaker to control my power states and multiplier settings. I can have 1, 2, 3, or all 4 of my cores overclocked. Core 1 hits 3.8ghz better than 2, 3, and 4; but I leave them all at 3.5ghz.

    10. Re:Huh? by mrmeval · · Score: 1

      It also reads like AMD bashing rather than tech article.

      --
      I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
    11. Re:Huh? by Athanasius · · Score: 2, Informative

      This might make things a little clearer for the Intel case. Certainly it gives more detail about how it works (for one thing it's not just a "base speed or Turbo speed" thing, there are multiple boost steps depending on the exact situation).

    12. Re:Huh? by gparent · · Score: 1

      Intel almost always gets better benchmarks regardless of the amount of cores. This also applies to gaming and application benchmarks, not just synthetic ones.

      As for power, the parent didn't mention it.

    13. Re:Huh? by Dogtanian · · Score: 1

      When will we stop referencing Moore's law?

      When it's clearly no longer true nor applicable- neither of which is the case yet.

      As a child I loved the TV show SPACE: 1999. But its gone now and not relevant

      That's because the moon was not- and has never been- catastrophically blasted from the Earth's orbit with Martin Landau and Barbera Bain onboard, running into countless humanoid-alien-of-the-weeks along the way.

      Moore's law was, and remains true, and a fundamental aspect of progress in the computer industry.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
    14. Re:Huh? by gstoddart · · Score: 1

      With older multi-core processors if you had a quad core 1.6ghz and you had a program that could only use 1 core then you would effectively just have a 1.6ghz processor

      See, my problem with this is the expectation that the application can use multiple cores. I don't care if an application can use multiple cores, I want the operating system to be able to make use of them.

      The day an application sees that I have four cores and can feel free to use all of them, we're pretty much hosed, because we'll have apps chewing CPU because they can. Most people are never CPU bound in the true sense of the word. Additional cores make it so that if one application is fairly busy the rest of the system is still usable.

      As soon as an application is capable of trying to use multiple cores, it will require multiple cores. And, I'm imagining a really annoying scenario whereby Office will require multiple cores so that it can run Clippy on a different one.

      I'm running more than just one piece of software at any given time, so I sure as hell don't want each of them to be trying to maximize how many CPUs they're using. Me, I've got VMWare, iTunes, several browser windows, and likely more at any given time -- if each app decides it wants to use all four of my cores, my overall system is going to be slower.

      Who the hell has a single application running that they need to squeeze as much performance as possible out of? You're talking very specialized apps. For the rest of us, an application exists in the context of many other things. Multiple cores make multi-tasking work very nicely, and I'd hate to start sacrificing that for an optimization to speed up a very small amount of apps which need to use as much CPU as available.

      --
      Lost at C:>. Found at C.
    15. Re:Huh? by AntiDragon · · Score: 2, Informative

      Performance on it's own isn't meaningful for everyone. If I'm setting up a server or better yet a data center, performance against cost has to be considered. And that's not just the cost of the hardware but also things like MTBF and power costs.

      I'm not implying that one is better than the other here, but a raw performance comparisson between like-for-like processors is not enough information to make spending decsion with. It may be better value to buy the system with poor performance and spend the savings elsewhere for example.

      --
      "...So I hung back and lurked. For 18 months. Can't beat a good old-fashioned lurking."
    16. Re:Huh? by gparent · · Score: 1

      The person I responded to wanted to make a choice regarding the performance of the two approaches, between Intel and AMD. He never mentionned anything about power consumption, heat, earthquakes and lady gaga apparitions. So I just answered his question, nothing more.

      I couldn't spend the savings elsewhere on my machine, by the way. More than 6 GB memory or a video card better than the 5850 isn't going to make up with the fact that the AMD offerings are just plain slow compared to the Intel processor I have.

    17. Re:Huh? by Wyatt+Earp · · Score: 1

      Thanks, I just got my first computer with an i series, an i7-820QM and was just curious how it all works, what with the four cores, eight cores and why its a 1.6 GHz chip that goes up to 2.8 GHz or more.

      My work machine is a 2 x Quad-Core Intel Xeon 2.8 GHz and wanted to figure out how the i7 mobility compared

      The article was lacking in my opinion.

    18. Re:Huh? by networkBoy · · Score: 1

      Virtual Dub Mod uses all cores available. It does so nicely. I finally go to the point with my system architecture that I'm CPU bound (previously I was severely I/O bound) and yes, the core OS UI suffers when it's running, but honestly I want that so my renders happen faster. If I didn't want that I would disallow one core to VdubM and have a snappy UI.

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    19. Re:Huh? by Anonymous Coward · · Score: 0

      The way I understand it (and I could be wrong) is that on a quad core 1.6ghz i7 each core is actually capable of going up to 2.8ghz, although I'm not sure if they are all capable of going to 2.8ghz at the same time.

      In theory they could (that is, the silicon is perfectly capable of doing so), in practice they aren't allowed to because of power constraints. The power control unit in the processor continuously adjusts clock frequency and supply voltage to keep the whole chip's power use equal to or less than the TDP (Thermal Design Power) rating Intel guarantees for that particular chip model.

      Most desktop i7s have a baseline clock rate much closer to the maximum, but this one is a mobile chip. Quad core mobile i7s are rated at 45W TDP, while desktop quad core i7s with a baseline speed of around 2.8 GHz are rated at 95W. That tells me the mobile i7 can probably run 2 cores at speeds close to 2.8 if the other two cores are completely idle (Intel can shut down power to idle cores so they use nothing, increasing the power headroom for other cores). With 3 cores active, it might settle on a clock speed somewhere in between. Load up all 4 cores, and it will have to drop down to 1.6 or thereabouts in order to avoid blowing past the 45W power budget.

    20. Re:Huh? by Gr8Apes · · Score: 1

      I did mention power as one option, and power directly implies heat.

      Honestly, Intel does get better benchmarks that are pure performance rated, within certain parameters. But lets say I want a 48 core machine, today. Intel doesn't have one, they only go up to 24 last I checked (4P still) . If I want low power passive cooling capable of watching HD video, that seems to be AMD also. If I want a machine that has performance that AMD meets, then the AMD is almost always less expensive than the Intel solution by as much as 30%.

      There's all sorts of benchmarks that aren't pure processing power that AMD and Intel compete quite well. Even the "max" benchmarks are interesting if you delve into the OC world (although I haven't seen the latest i7 OC benches, so again, this is probably all out of date).

      For instance, right now I own a Core 2 Q6600 and a Phenom II X4 810, both running 4GB DDR2. I can't tell the difference between them performance wise. (Yes, the Phenom is about 12 months newer.... I know, but it was also $100 less when bought than the Intel chip) I don't run on the bleeding edge. I probably will buy an i7 chip in the next year, or a 6 core AMD chip ($200? If it runs on DDR2, I may buy one now) as what I need them for utilizes lots of threads and cores quite well.

      --
      The cesspool just got a check and balance.
    21. Re:Huh? by gparent · · Score: 1

      I did mention power as one option, and power directly implies heat.

      Oh, you definitely did, I meant Wyatt. And definitely go AMD for low cost/power.

    22. Re:Huh? by gparent · · Score: 1

      Apparently its max frequency is quite high with Turbo on, damn. I have a i7 930 here (OCd so I turned Turbo mode off) and if I had Turbo mode on it wouldn't be nearly as fast.

  3. Re:No turbine, no turbo by poopdeville · · Score: 1
    --
    After all, I am strangely colored.
  4. Cooling fan noise anyone? by Twinbee · · Score: 1

    Rather than cranking up the GHz of each core to obtain more speed, I wish they'd concentrate on keeping it cool. I hate the fan noise, and multicore was a way around that because it rarely heats up with standard usage. Hence less or no cooling required.

    "We've got to find some way to get that fan to rotate to annoy the users... ah I have a cunning plan..."

    --
    Why OpalCalc is the best Windows calc
    1. Re:Cooling fan noise anyone? by Anonymous Coward · · Score: 1, Informative

      try passive cooling. http://www.vonslatt.com/proj-cc.shtml

    2. Re:Cooling fan noise anyone? by washu_k · · Score: 5, Informative

      There are a multitude of aftermarket CPU coolers which are much quieter than the stock ones from Intel or AMD. Some chips can even be run passive with the right heatsink. Take a look at the reviews on http://www.silentpcreview.com/

    3. Re:Cooling fan noise anyone? by ozbird · · Score: 2, Interesting

      Do both.

      I bought an Intel i7-860 recently and the supplied HSF is barely able to keep the core temperatures under 95 deg. C with eight threads of Prime95 running. Eek!! I replaced it with a cheap Hyper TX3 cooler (larger coolers won't fit with four DIMMs fitted), and it run at least 20 degrees C cooler under the same conditions. The supplied fan is a little noisy under full load, but for gaming etc. it's not a problem.

      Turbo Boost is cute, but I've opted to overclock it at a constant 3.33GHz (up from 2.8GHz) instead for predictable performance, with no temperature or stability issues. YMMV.

    4. Re:Cooling fan noise anyone? by DAldredge · · Score: 1

      Then buy one of the low voltage / extreme low voltage variants that AMD and Intel both make.

    5. Re:Cooling fan noise anyone? by Anonymous Coward · · Score: 0

      I put my current system together 16 months ago (Core i7-920). Watching core temperatures get pretty high (79 degrees Celsius, or 174 degrees fahrenheit). I noticed that in testing these chips, Intel used a thermalright cooler instead of their stock box cooler. I got a Thermalright true 120, and replace the boxed cooler, and watched the temperature drop 10 degrees at the top end and 20 degrees at the bottom, and it takes a much longer time to get warm.

    6. Re:Cooling fan noise anyone? by rwa2 · · Score: 1

      Get a goat.

      Then after it craps in your bed and chews up your linens and brays all night, get rid of it.

      Your computer will seem so much cooler and quieter after you get rid of the goat!

      (my current PC from 2007 is soooo much quieter than the 2002-era PC it replaced)

    7. Re:Cooling fan noise anyone? by SanityInAnarchy · · Score: 4, Interesting

      predictable performance

      Predictable power-drain, you mean, and a predictable shortening of the life of your hardware -- assuming it doesn't just overheat and underclock itself, which I've seen happen a few times.

      CPU scaling has been mature for awhile now, and it's implemented in hardware. Can you give me any real examples of it causing a problem? The instant I need that speed (for gaming, etc), it's there. The rest of the time, I'd much rather it coast at 800 mhz all around, especially on a laptop.

      with no temperature or stability issues. YMMV.

      Understatement of the year.

      Overclocking is a bit of a black art, for a number of reasons. First problem: How do you know it's stable? Or rather, when things start to go wrong, how do you know if it's a software or a hardware issue? The last time I did this was a 1.8 ghz machine to 2.7. I ran superpi, 3dmark, and a number of other things, and it seemed stable, but occasionally crashed. Clocked it back to 2.4, it crashed less often, but there were occasionally subtle filesystem corruption issues -- which was much worse, because I had absolutely no indication anything was wrong (over months of use) until I found my data corrupted for no apparent reason. Finally set it back to the factory default (and turned on the scaling) and it's been solid ever since.

      Second problem: Even with the same chip, it varies a lot. All that testing I did is nothing compared to how the manufacturer actually tests the chip -- but they only test what they're actually selling. That means if they're selling you a dual-core chip that's really a quad-core chip with two cores disabled, it might just be surplus, the extra cores might be fine, but they haven't tested them. Or maybe they have, and that's why they sold it as a dual-core instead of quad-core.

      So even if you follow a guide to the letter, it's not guaranteed.

      I'm sure you already know all of the above, but I'm at the point in my life where, even as a starving college student, even as a Linux user on a Dvorak keyboard, it's much saner for me to simply buy a faster CPU, rather than trying to overclock it myself.

      --
      Don't thank God, thank a doctor!
    8. Re:Cooling fan noise anyone? by electrosoccertux · · Score: 1

      blah blah blah, get with the times old folks with small UIDs. A hefty majority of the build-your-own-pc crowd overclocks.

      We test with a multitude of stress testing programs that test all parts and instructions of the architecture. We find the maximum frequency we can run at acceptable voltage and heat. There's a linear region of overclocking and an exponential region. Most people find the divergence point and sit there. Those with water cooling can go a little further.

      It pretty much is guaranteed, because 90% of us have figured it out and run our rigs overclocked. Head over to anandtech forums and look at the rigs people have listed in their signatures at the end of posts. 4Ghz core i7's all over the place, 3.8ghz Ph2's all over the place...

      it's much saner for me to simply buy a faster CPU, rather than trying to overclock it myself.

      Cool. Scroll down to the graph.
      At the time I made the purchase the Core 2 Extreme x6800 cost $999. My e2180 cost $108. It hit 3.4ghz on the nose with 1.48v no sweat, never locked up in anything.
      Feel free to blow $900. For me it was a cheap, fun hobby while I was in school.

    9. Re:Cooling fan noise anyone? by ozbird · · Score: 1

      Predictable power-drain, you mean and a predictable shortening of the life of your hardware -- assuming it doesn't just overheat and underclock itself, which I've seen happen a few times.

      Assume away. I'll repeat myself: at full load the replacement heatsink runs substantially cooler than the stock (and warrantied) Intel cooler. The Intel cooler at 90+ deg. C - barely within the thermal specs. for the CPU - did not thermal trip; why would the replacement cooler trip at 65 deg. C?! Your overclocking examples pushed the core 50% and 33% above spec. - it's hardly a surprise that you had issues! My setup is a more modest 12.5% overclock with corresponding memory multiplier reduction to keep it at its stock speed (1600MHz.) With Turbo Boost, the CPU is overclocked to the same speed with two cores loaded, and less that one core loaded (3.46GHz) - it's hardly pushing the envelope.

    10. Re:Cooling fan noise anyone? by GigaplexNZ · · Score: 1

      I say that as preface to the following comment:

      They're not coolers, they're fucking fans. Get over it.

      Are you sure about that? My aftermarket CPU cooler (aka "fucking fan") is a large heat sink with heat pipes and no rotating parts.

    11. Re:Cooling fan noise anyone? by SanityInAnarchy · · Score: 1

      At the time I made the purchase the Core 2 Extreme x6800 cost $999. My e2180 cost $108.... Feel free to blow $900.

      Yes and no.

      Yes, I would much rather "blow" $900 than wonder WTF is wrong with my computer after I thought I'd figured this out:

      We find the maximum frequency we can run at acceptable voltage and heat.

      I value my data much more than that $900. It can also be worked out in terms of real effort -- last time I was working, I made $20/hour, so that $900 works out to about 45 hours. I easily spent more time than that building my own computer and trying to overclock it properly. I understand that it's enjoyable, but not nearly as much as my real job was.

      However, in the real world, I doubt I'd spend more than $100 or $200 on a CPU, partly because I have some patience. Where's the appeal in spending all that time and money, not to mention the risk, when that "extreme" whatever will be a commodity in another year or two?

      --
      Don't thank God, thank a doctor!
    12. Re:Cooling fan noise anyone? by SanityInAnarchy · · Score: 1

      Your overclocking examples pushed the core 50% and 33% above spec. - it's hardly a surprise that you had issues!

      I don't remember if I went directly from 2.4 back to 1.8, or if I tried some steps in between. I do remember that, again, it was mostly stable, survived every actual test I threw at it, and yet still had subtle issues that I only discovered through real use.

      It just wasn't worth it, especially when it wasn't particularly long before I replaced that single-core 1.8 with a cheap dual-core 2.4.

      YMMV, but when I have a job, my time is worth more than the small amount of money it might cost me to buy more hardware, or upgrade more often. When I don't have a job, I can't afford to risk damaging my hardware and having to spend even more.

      --
      Don't thank God, thank a doctor!
    13. Re:Cooling fan noise anyone? by electrosoccertux · · Score: 1

      At the time I made the purchase the Core 2 Extreme x6800 cost $999. My e2180 cost $108.... Feel free to blow $900.

      Yes and no.

      Yes, I would much rather "blow" $900 than wonder WTF is wrong with my computer after I thought I'd figured this out:

      We find the maximum frequency we can run at acceptable voltage and heat.

      I value my data much more than that $900. It can also be worked out in terms of real effort -- last time I was working, I made $20/hour, so that $900 works out to about 45 hours. I easily spent more time than that building my own computer and trying to overclock it properly. I understand that it's enjoyable, but not nearly as much as my real job was.

      However, in the real world, I doubt I'd spend more than $100 or $200 on a CPU, partly because I have some patience. Where's the appeal in spending all that time and money, not to mention the risk, when that "extreme" whatever will be a commodity in another year or two?

      How did it take you 45 hours to overclock it? I finished in about 45 minutes. It's simple, set voltage to something higher but within the CPU spec, clock the core up while you're running Prime95 as a preliminary test, up 100Mhz, another 100Mhz, etc...when you get close to the known limit of the chip (3.2Ghz for the e21x0 series of chips when I had that one) you clock it up 30 Mhz...another 30Mhz... Prime95 errors out before the computer completely locks up, so then you back off 100Mhz or so, check your temps to make sure you're good, and then start Prime95 again and leave it running as you go to work, go to bed, or whatever. If you're still running within 6hours, you're good to go.

      I've been overclocking for 5 years and have yet to have any data corruption. Partly that depends on the architecture, and partly on if you've got your hard drives connected to the locked SATA ports.

    14. Re:Cooling fan noise anyone? by SanityInAnarchy · · Score: 1

      How did it take you 45 hours to overclock it?

      I'm not measuring the time to overclock, though that alone was several hours -- reading up on how to test it, finding the right settings, tweak, tweak a little more, make sure it works, meanwhile endless reboots to boot Windows and run Prime95 or SuperPI, then reboot to the BIOS to tweak settings, read forums to find out the right settings to use...

      If you're still running within 6hours, you're good to go.

      So in addition to what I discussed above, my shiny new computer is completely unusable for much longer than just 45 minutes while I do all of the above.

      And remember, that was just the first part. Rinse and repeat in a few weeks when I get sick of my computer crashing for no apparent reason -- and that's after spending several hours trying to figure out whether it was a software problem or not, running various antivirus/antispyware tools, reinstalling Windows to see if that helps, trying a different filesystem on Linux, etc.

      And then do it again when clocking it back didn't help. And then again.

      Keep in mind, in each of these cases, it did have something like Prime95 running overnight without issues. It was rock-solid stable, except the few moments when it wasn't. It only takes a few moments to baloon into hours trying to figure out WTF went wrong.

      If nothing else, going with the stock settings means I can at least eliminate an improper overclock from the list of things to check when shit starts to break. It means I now have a fairly reliable set of tools to test hardware (check SMART, run memtest), and if that works, I can assume it's a software problem and work from there.

      You also ignored the point about patience. Why even spend the 45 minutes (plus the extra time without a usable computer) when a cheap, stock PC available in another 2 years will easily be faster than your custom overclocked rig?

      I've been overclocking for 5 years and have yet to have any data corruption. Partly that depends on the architecture, and partly on if you've got your hard drives connected to the locked SATA ports.

      Locked what now? And why does this matter, considering I had no issues at all once I turned off the overclock?

      --
      Don't thank God, thank a doctor!
    15. Re:Cooling fan noise anyone? by electrosoccertux · · Score: 1

      depending on the architecture and bus, the SATA frequency can vary if you're playing with the FSB. It's usually the last 2 ports, ie if you've got 6 it'd be 5 and 6, it's usually in the manual. If you touch the bus frequency and that affects the SATA ports any, WHAM there's your data corruption. I had a friend that learned the hard way.

      as for why spend 45 minutes, it's because that $100 chip was noticeably faster when overclocked, and I needed that "fast" _now_ from the cheapest component possible, to play Unreal Tournament 3.

    16. Re:Cooling fan noise anyone? by SanityInAnarchy · · Score: 1

      depending on the architecture and bus, the SATA frequency can vary if you're playing with the FSB. It's usually the last 2 ports, ie if you've got 6 it'd be 5 and 6, it's usually in the manual. If you touch the bus frequency and that affects the SATA ports any, WHAM there's your data corruption.

      Hmm. That could be it -- though again, it worked fine, often for weeks or months at a time, before I'd actually see the corruption (or crashes).

      See? More trivia I'd have to learn, certainly not something I'd necessarily find out in 45 minutes.

      I needed that "fast" _now_ from the cheapest component possible, to play Unreal Tournament 3.

      I would again ask why -- a cheap computer now can play amazing games from 2-3 years ago. That also means that much more time for the community and reviewers to filter out the games that are crap, for the developer to fix the bugs, and for the DRM to be well and thoroughly cracked.

      I'm also a bit skeptical that any game, new or not, needs $900 worth of CPU power alone.

      And while I might actually accept the risk of screwing something up on a gaming machine, my current one is also a work machine, which makes sense -- if I'm going to build something powerful enough to game, it's also going to be a lot nicer to work with. With that in mind... If me screwing up part of the overclock results in my savegame being corrupted, or my game machine crashing, that's one thing. If it results in work being corrupted, or my work machine crashing in the middle of the day, that's a bit worse.

      --
      Don't thank God, thank a doctor!
    17. Re:Cooling fan noise anyone? by electrosoccertux · · Score: 1

      The community never went to UT3, I played instagib capture the flag exclusively.
      You're welcome to do what you like but it's not really my job to convince you I wanted to play the newest game.
      I was simply trying to point out it's nowhere near as bleak a situation as you seem to think. I think you just had a bad overclocking experience, tons of people have good ones and never have a problem. For poor people, we love to do it-- because it _can_ be done right.

      The Crysis games are still CPU limited in areas. If you want to play that game at full settings you need an overclocked i7 rigt with 3x 5870s or 3 gtx480's, etc.

    18. Re:Cooling fan noise anyone? by electrosoccertux · · Score: 1

      and again, I've never had these corruption issues, and I've been running overclocked for the last 6 years.
      part of desiring the fast computer is simply because of the engineering marvel of it. $100 CPU, made to run as fast as a $999 CPU. If you can do it without any problems whatsoever (and I had NONE ever with that rig), and can do it in 45 minutes, then why not?

  5. PS. by sznupi · · Score: 3, Interesting

    For that matter, can we have one more thing: a way to limit max core usage to, say, 10% (imagine you're playing an old game on a laptop, for example Diablo2; now, many games have the unfortunate habit of consuming all available CPU power...whether they need to or not; taking battery with them)

    --
    One that hath name thou can not otter
    1. Re:PS. by icebraining · · Score: 4, Informative

      aptitude install cpulimit

    2. Re:PS. by bhtooefr · · Score: 2, Informative

      It's called SpeedStep. (OK, it doesn't reduce the CPU usage, but it reduces the CPU clock speed, which is more effective.)

    3. Re:PS. by Anonymous Coward · · Score: 0

      man cpulimit. man numactl.

    4. Re:PS. by sznupi · · Score: 2, Insightful

      Yes, one can force SpeedStep setting - but the game would still be consuming all available power, preventing the CPU from going to pseudo sleep states (which is even more effective)

      --
      One that hath name thou can not otter
    5. Re:PS. by fedcb22 · · Score: 2, Insightful

      Really? I always thought that going to a lower voltage mode was much more effective than C1/C2/C3. That's why SpeedSted is used, against normal CPU throttling.

    6. Re:PS. by Animaether · · Score: 2, Informative

      In the off chance that you're running on Windows;
      http://mion.faireal.net/BES/
      ( ugly UI, does the job )

    7. Re:PS. by sznupi · · Score: 2, Interesting

      What do you mean "that's why SpeedStep is used, against normal CPU throttling"? SpeedStep is CPU throttling; but on top of that C-states are also highly effective, or at least Thinkpad Wiki thinks so, and I see no reason to disbelieve them...

      --
      One that hath name thou can not otter
    8. Re:PS. by bemymonkey · · Score: 1

      RMClock does CPU-Throttling. That may be what you're after...

    9. Re:PS. by fedcb22 · · Score: 1

      Sort of. Speedstep actually changes the frequency / voltage of the processor, whereas normal CPU throttling just limits the amount of processing power available.

    10. Re:PS. by L4t3r4lu5 · · Score: 1

      DIablo 2 runs on Linux? I've never played it... I might just have a reason now (Having WoW as the only running game is getting VERY boring).

      --
      Finally had enough. Come see us over at https://soylentnews.org/
  6. Summary? by sakonofie · · Score: 1

    Both do the following: they detect when some cores are being unused, they then give less power and decrease the clock speed to some of less used cores, and the power/clockspeed is then increased on the rest of the cores. The AMDs have do this by having 2 different of modes of operation with fixed power distribution/clockspeed settings for each mode. Intel does something more dynamic and on-the-fly.

    Now I might have mis-summarized the article, but shouldn't that have been the article summary instead of a rephrasing of the article's lead?

  7. Moore's Law? by Anonymous Coward · · Score: 0

    The article seems to have absolutely no relationship to Moore's Law, or to whatever the author imagine's Intel's "corporate philosophy" to be.

    Why is that extraneous, off-topic garbage included in the summary?

  8. "Apparent performance" by macshome · · Score: 4, Insightful

    What's "apparent performance"? It's either faster or it's not.

    1. Re:"Apparent performance" by asdf7890 · · Score: 3, Insightful

      What's "apparent performance"? It's either faster or it's not.

      You have obviously never worked in UI design! (though in this area I don't know who/what they would be trying to fool or how they would be trying to fool them/it so your response is probably quite right)

    2. Re:"Apparent performance" by phantomcircuit · · Score: 4, Insightful

      Many programs simply do not benefit from multiple cores. This technology is basically a trade off between partially disabling one core and increasing the frequency of the other core.

    3. Re:"Apparent performance" by pwnies · · Score: 4, Interesting

      Not necessarily. If they're overclocking a single core, while underclocking the rest, it may all balance out to have an average core speed that's less than what it was. However, in doing this it may actually increase performance if there is a single app that requires a lot of CPU time (and isn't threaded). In reality the total speed of the computer is being reduced, while the performance as viewed by the user is increasing.

    4. Re:"Apparent performance" by oldhack · · Score: 1

      Ah! The infamous progress bar.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    5. Re:"Apparent performance" by Anonymous Coward · · Score: 0

      No, that's just not so. And that's *exactly* the problem with people comparing software packages. Somehow people have no trouble describing the benefits and costs of an SUV vs. a smart car, but insist on packaging aspects of software tightly into a single number (it's not just software -- IQ has the same problem, for example).

      Almost nothing is "either faster/better/warmer/more secure/etc. or it's not", unless you get ridiculously specific. Otherwise we'd all use CPUs for graphics or GPGPUs for general processing, instead of having both.

      There's tradeoffs that apply to pipeline lengths (for clock speed) vs. branch misprediction costs that matter differently for different scenarios, there's the article's given tradeoff of multicore parallelism vs. clock speeds, there's instruction reordering, there's hardware scheduling you can do to give important hardware threads priority for hyperthreading/equivalents such that you get the same overall instruction throughput but the UI updates at a faster schedule, etc., etc., etc..

    6. Re:"Apparent performance" by Hurricane78 · · Score: 1

      You have obviously never worked in UI design! (though in this area I don't know who/what they would be trying to fool or how they would be trying to fool them/it so your response is probably quite right)

      And apparently you have never worked in sentence design. ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    7. Re:"Apparent performance" by Jah-Wren+Ryel · · Score: 1

      You have obviously never worked in UI design! (though in this area I don't know who/what they would be trying to fool or how they would be trying to fool them/it so your response is probably quite right)

      And apparently you have never worked in sentence design. ;)

      And anyone correcting typos on a web-forum obviously has no girlfriend.

      --
      When information is power, privacy is freedom.
  9. A better explanation by Sycraft-fu · · Score: 5, Informative

    The article kinda glosses over things. So a more detailed explanation of how Intel's turbo boost works:

    As stated, every core has a budget for the maximum heat it can give off, and the maximum power it can use, as well as a max clock speed that it can handle. However, when you look at these things, they aren't all even, one ends up being the limiting factor. So Intel said, ok, we design a chip to always run at a given speed and stay under the thermal and power envelopes. However, if it isn't running at that, we allow for speed increases. It can increase the speed of cores in 133MHz increments. If things go over, it throttles it back down again.

    This can be done no matter how many cores are active, but the less that are active the more it is likely to be able to be. On desktop cores, it isn't a big deal since they usually run fairly near their speed limit anyhow. So you pay see only 1 or 2 max 133MHz increments that can happen. For laptop cores, in particular quad cores, it can be a lot more.

    The Intel i7-720QM runs at 1.6GHz and has 1/1/6/9 turbo boost multipliers. That means with all 4 cores running, it can clock up at most 1 increment, to 1.73GHz. However with only one running, it can go to 2.8GHz, 9 133MHz clocks up. It allows for a processor that would be too fast to reside in the laptop to go in there with some flexibility. A desktop Core i7-930 is 2.8GHz with 1/1/1/2 turbo mode. That means it'll clock up to 2.93GHz with 2-4 cores active, and 3GHz with 1. Much less flexible, since it is already running near it's rated max clock speed.

    Now this is not the same as speed step, which is their technology to down clock the CPUs when they aren't in so much use. Similar idea, but purse based on how hard the CPU is being asked to work, not based on if the system can handle the higher speeds.

    As an aside, I'll call BS on the "Little uses multiple cores." Games these days are heavily going at least dual core, some even more. Reason is, if nothing else, the consoles are that way too. The Xbox 360 has 3 cores, 2 threads each. The PS3 has a weak CPU attached to 7 powerful SPUs. On a platform like that, you learn to do parallel or your games don't look as good. Same knowledge translates to the PC.

    However there are still single core things, hence the turbo boost thing can be real useful. In laptops this is particularly the case. If the i7 quad was limited to 1.6GHz, few people would want it over one of the duals that can be 2.53GHz or more. Just too much loss in MHz to be worth it. However now, it can be the best of all worlds. A slower quad, a faster dual, whatever the apps call for, it handles.

    1. Re:A better explanation by Vellmont · · Score: 0, Troll


      As an aside, I'll call BS on the "Little uses multiple cores." Games these days are heavily going at least dual core, some even more.

      I'd say games qualify for "little uses". Believe it or not, most people don't use their computers for high end gaming.

      Even for games, are you really certain that the extra cores are used much? Sure, the game can say it uses multiple cores, and I'm sure it actually does. But how much does it really improve performance?

      The PS3 has a weak CPU attached to 7 powerful SPUs.

      Heh. The PS3 is known to be notoriously difficult to program as well. How many tasks can really be split up into 7 relatively equal, independent parts?

      --
      AccountKiller
    2. Re:A better explanation by juuri · · Score: 2

      What I find interesting is that the current OS most people use, with the exception of
      some RealTime and big iron custom dealies are still built in such a monolithic way that
      it becomes more "profitable" to the user experience to still ramp up single cores as
      opposed to having most cores running at the same speed.

      With the exception of some high demand apps like games, extensive math apps,
      and stuff that could or should be offloaded to GPUs desktop OS don't need a VERY
      fast single core, they instead need lots of equal cores with fast context switch times
      coming from the OS.

      For example the fastest core in Win7/OSX for a desktop should be the one handling
      the UI but it doesn't need to be THAT much faster than anything else. Instead all the
      tiny little apps need to be sent around to as many different cores as possible when
      they aren't multithreaded... unfortunately none of the current schedulers are that great
      at this in consumer land. Even worse the kernels can have so much locked in that
      you end up with lots of things stuck on a single core that could exist elsewhere.

      Such a shame that true mach never got the switch times down because of the
      huge separation in "drivers" or "kernel features". QNX definitely got this right,
      but they never took multicores seriously, perhaps it is a much harder problem than
      I am assuming.

      --
      --- I do not moderate.
    3. Re:A better explanation by DMalic · · Score: 4, Informative

      The third core gives a significant performance benefit over two cores, especially since many games were originally designed for consoles and are badly ported to PCs. Unoptimized performance hogs like Grand Theft Auto demand more cores (and can use them). Just today I saw an article on Anandtech describing significant, unexpected benefits from a slower quad core over a newer, faster dual-core in gaming. http://www.anandtech.com/show/3695/the-clarkdale-experiment-mea-culpa

    4. Re:A better explanation by drsmithy · · Score: 1

      I'd say games qualify for "little uses". Believe it or not, most people don't use their computers for high end gaming.

      Most people don't use their computers for high end _anything_ and whether the machine has one core or a dozen is basically irrelevant.

    5. Re:A better explanation by petermgreen · · Score: 2, Insightful

      I'd say games qualify for "little uses". Believe it or not, most people don't use their computers for high end gaming.
      Afaict most people don't use their computers for anything that strains the CPU at all. Most people would be perfectly happy with a bottom of the range C2D, i3, late P4 or maybe even less as long as the system was kept free of crapware and had enough ram for their OS and applications of choice.

      However of those apps that DO strain the CPU (e.g. games, video encoding, scientific software, software build systems) a lot do now have the ability to use multiple cores.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  10. Re:No turbine, no turbo by CorporateSuit · · Score: 1

    It may have no turbines, but it does have an oscillator!

    --
    I am the richest astronaut ever to win the superbowl.
  11. slowing down? by Anonymous Coward · · Score: 0

    What this article describes, is more like
    "slowing cores down" to save energy, rather than "speeding up the cpu".

    1. Re:slowing down? by Anonymous Coward · · Score: 0

      Yes, except for the bit where they burn off the energy saved to overclock the cores that aren't slowed down -- did you even read the article?!

    2. Re:slowing down? by Anonymous Coward · · Score: 0

      Whoops -- forgot I was posting on /., not e)))).

      Now I just wonder why the hell nobody's zinged me with "YMBNH, nobody RTFAs." yet.

  12. Obligatory reference... by Hamsterdan · · Score: 1

    But will it allow me to jump over those traffic jams?

    http://www.youtube.com/watch?v=arL04K3HLMw

    --
    I've got better things to do tonight than die.
  13. Why not use the extra transistors... by John+Hasler · · Score: 2, Interesting

    ...for more cache instead of more processors? Think of something with as many transistors as a hex core but with only two cores and the rest used for L1 cache! I'd suggest lots more registers as well, but that would mean giving up on x86.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:Why not use the extra transistors... by maxume · · Score: 1, Insightful

      They like to use cache size to segment markets (people that really need it end up paying for it).

      Also, I imagine that they ran the numbers on increased cache size versus another core (but maybe they figured the second core was more marketable, rather than a better performance boost).

      I do however, have this wishy-washy impression that Intel has been selling Pentium Pros with ever larger caches and ever lower voltages for the last 10 years (I'm quite certain that the Pentium III was mostly a smaller, faster Pentium Pro; The II and IV were not. I think Core was, except for there being 2 of them.). Somebody please either lambaste this or tell me it isn't that far off.

      --
      Nerd rage is the funniest rage.
    2. Re:Why not use the extra transistors... by glsunder · · Score: 4, Interesting

      Larger caches are slower. Moving to a larger L1 cache would either require that the chip run at a lower clock rate, or increase the latency (increasing the length of time it takes to retrieve the data).

      As for registers, they did increase them, from 8 to 16 with x64. IIRC, AMD stated that moving to 16 registers gave 80% of the performance increase they would have gained by moving to 32 registers.

    3. Re:Why not use the extra transistors... by sznupi · · Score: 2, Interesting

      PII is also of the PPro lineage. And even if PII, PIII and to some degree P-M and Core1 aren't that different, there are supposed to be some notable changes with Core2 and, especially, Nehalem.

      Besides, if the tech is good and it works... (look what happened when they tried "innovating" with PIV)

      --
      One that hath name thou can not otter
    4. Re:Why not use the extra transistors... by DMalic · · Score: 2, Interesting

      It's more like a series of improvements on that model. It works really well, though. Cache doesn't seem to help performance as much as you'd think it would, though. There are some core2 cpus described as "pentium dual core" with a fraction of the cache which perform almost as well.

    5. Re:Why not use the extra transistors... by Anonymous Coward · · Score: 1, Funny

      Screw that.. Give me faster ram and stack it between heat pipes on top of the cpu..

    6. Re:Why not use the extra transistors... by petermgreen · · Score: 2, Insightful

      L1 and sometimes L2 caches are small not because of die area but because there is a tradeoff between cache size and cache speed. Only the lowest level cache (L3 on the i series) takes significant chip area (and it already takes a pretty large proportion on both the quad and hex core chips).

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    7. Re:Why not use the extra transistors... by SpazmodeusG · · Score: 1

      Because the cache is shared on newer multicore processors you essentially do get more cache. Cache is the largest user of real estate on die. The added processors you get are just a bonus.

    8. Re:Why not use the extra transistors... by Anonymous Coward · · Score: 1, Interesting

      Some architectures are more dependent on cache size than others; the Pentium 4 was awful when cache-starved -- the first round of P4-based Celerons were utter dogs with only a 128k L2 cache and 400FSB, for example, while the jump from Northwood (512k L2) to Prescott (1MB L2) actually hurt performance for many workloads as the cache increase didn't really help with the increase in pipeline length and the clock speeds didn't scale up initially. By contrast, the jump in performance from 533FSB to 800FSB dual-channel between the B and C northwoods was big.

      Core 2 was a remarkably more tolerant of slow memory and smaller caches.

    9. Re:Why not use the extra transistors... by Anonymous Coward · · Score: 0

      Also, with out of order processors, you've got a lot more registers "behind the scenes" than you have through the visible instruction set architecture. I think it was around 40 with the P6 (PPro, PII, P3) and around 120 starting with the P4 (I'm fairly sure that this was one of the things that was updated from the P3 to the P-M as well)

    10. Re:Why not use the extra transistors... by drsmithy · · Score: 1

      Somebody please either lambaste this or tell me it isn't that far off.

      Oversimpliyfing...

      The PII was a PPro with an off-die L2 cache and MMX. The PIII was a PII with SSE. The Pentium M was a PIII with a P4 FSB and SSE2.

    11. Re:Why not use the extra transistors... by bernywork · · Score: 1

      IIRC, Intel got their head handed to them by AMD when they "lost" the Mhz race to AMDs Marketing dept.

      Intel with the P4 had a very long pipeline which they could crank the speed of faster than what AMD could. On the other hand, AMD went for multiple shorter pipelines though the CPU which meant that most of what people did went through the CPU faster. (I am purposefully skipping over cache misses, delays on getting things through the pipeline etc) The benchmarks at the time proved it. Also, the addition of the on-die memory controller and Hyper Transport meant that AMD's memory bandwidth was a lot faster.

      After this, when Intel realised that the longer pipeline was killing them, and they went down the road of wide order execution, same as AMD. To do this, they effectively dropped the long pipeline of the P4 series and went back and re-developed a new core from the Pentium III train.

      At least they admitted they fucked up and fixed it, they would be dead by now if they hadn't.

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
    12. Re:Why not use the extra transistors... by drinkypoo · · Score: 1

      As for registers, they did increase them, from 8 to 16 with x64. IIRC, AMD stated that moving to 16 registers gave 80% of the performance increase they would have gained by moving to 32 registers.

      AMD64 retains the index registers &c and increases general purpose registers from 4 to 16, not 8 to 16. And to be totally critical, x86 has zero general-purpose registers, because many (most?) instructions require that operands be in specific registers, and that the result will be placed in a specific register. Those other four registers are specific-purpose as well, you usually can't even use them to temporarily hold some data because you need to put addresses in them to execute instructions. x86 has four more or less general purpose registers. It is a testament to the achievements of both AMD and intel engineers that you only get ~15% improvement in performance when quadrupling the number of GPRs and doubling their length (i.e., a simple recompile often offers such an improvement.)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    13. Re:Why not use the extra transistors... by sznupi · · Score: 1

      They didn't lost it just to marketing department of AMD. Athlons were simply a better core, capable of higher clocks (and without such obvious tricks as with P4; they had often higher IPC than P3)
      If anything, Intel was driven too much by marketing back then... (remember P3 Coppermine 1.13 GHz fiasko?)

      --
      One that hath name thou can not otter
    14. Re:Why not use the extra transistors... by swilver · · Score: 1

      So 32 registers would gain another 20%? I don't know, but that seems definitely worth it...

    15. Re:Why not use the extra transistors... by bernywork · · Score: 1

      Well, Intel tried ramping up the Mhz to try to compensate for the longer pipeline, and then tried to claim that they were faster. AMD just printed a larger number on the box without increasing the Mhz of the core. Yes, in a lot of instances AMD were faster, however, when someone who hasn't read the benchmarks goes to buy a computer they look at the numbers and if they see Athlon 3400 and a P4 3200 they are going to presume that the Athlon is faster because it's got a larger number. Hence, they got out marketed by AMD.

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
    16. Re:Why not use the extra transistors... by sznupi · · Score: 1

      But I was thinking about the initial circumstances of "IIRC, Intel got their head handed to them by AMD when they "lost" the Mhz race to AMDs Marketing dept." (after all, my post started from the times of PPro & K5) - it wasn't just to AMD Marketing dept., Athlons were clearly more capable vs. P3.

      Anyway, as to the later numbers printed next to "Athlon XP", they were quite accurate IIRC, often rather conservative (placing given core under a notch higher number wouldn't be a stretch). If that wouldn't be the case, you can be sure Intel marketing would really take AMD on a bumpy ride.

      --
      One that hath name thou can not otter
    17. Re:Why not use the extra transistors... by Bengie · · Score: 1

      More L1 cache = more latency

      Much of this latency could be compensated by your more registers idea.

      Too bad you're still limited to one instruction per second. All those registers are only good at reducing requests back out to the L1.

      'All in all, you'll have to have a ton of code re-written and to gain a small sub double-digit percentage on single threads and running much slower but costing the same as a multi-core setup on thread-heavy tasks.

      In other words, this is only good for a niche market

      You also run the issue that a single core can only get so large before you start to do what they did with the P4 and put stall stages in the pipeline to give signals time enough to propagate across the chip.

  14. Turbo button comming back? by TavisJohn · · Score: 2, Funny

    So they are bringing the Turbo Button back?

    Seriously, When I was looking at laptops, 2 laptops that were pretty much the same in specks, one had a "Turbo" CPU the other's CPU was the speed of the "Boosted" one next to it...
    The price difference... $20.00!!! I'll pay an extra $20 to have FULL SPEED ALL THE TIME!

    1. Re:Turbo button comming back? by broken_chaos · · Score: 1

      No, this is automatic at the hardware level -- not a manual switch. In fact, it's more or less useless on desktop machines (as someone excellently explained above) since the speed improvements are small. On laptops with >2 cores, however, it seems to be very, very nice. A fairly easy way to have both reasonably powerful parallel processing with multiple cores, fairly fast single-thread processing, and not creating a level of heat that could damage components.

      Also, if you're overclocking a desktop (which is insanely easy on any modern chip), it'll probably be the first thing you turn off. Boosting the speed in one core unpredictably can both cause instabilities at higher overclocks and is even more pointless than normal, as you're almost certain to get much higher speeds at all times out of the chip than it would have run at even with the highest 'turbo' mode at default settings.

    2. Re:Turbo button comming back? by dwinks616 · · Score: 1

      $20 more for what? A processor that runs hotter "ALL THE TIME", uses more battery "ALL THE TIME" and requires louder fans "ALL THE TIME". No thanks, I prefer my laptop to be cool, quiet and have long battery life. If I can save $20 in the process, that's just a bonus.

    3. Re:Turbo button comming back? by PitaBred · · Score: 1

      That turbo boosted CPU also had hyperthreading, AES-NI and a few newer instruction sets, and will last longer on battery. I can't imagine why you'd want battery on a laptop, though... it's all about teh megahurz!

  15. Why? by Bootarn · · Score: 2, Insightful

    Why this compromise? There's a huge need for developers to start thinking in terms of multicore CPUs. Offering them this solution is just postponing the inevitable. We need change now.

    1. Re:Why? by Shikaku · · Score: 4, Insightful

      Because it's a pain in the ass and very hard for most coders.

      What we need is either a simple library for threading or a new language (like haskell) for auto-parallelization

    2. Re:Why? by ascari · · Score: 1

      Erlang anyone?

    3. Re:Why? by Anonymous Coward · · Score: 2, Insightful

      And more importantly, not all tasks CAN be parallelized.

    4. Re:Why? by Anonymous Coward · · Score: 0

      There are plenty of simple libraries for threading, for nearly every language imaginable. The problem is that threading is in general a terrible abstraction. It exposes all the worst aspects of concurrent non-determinism upward to application code, while hiding most of the low-level facilities present in hardware for managing it. So in practice it needs a cumbersome library built on top of the threading to hide most of what threading exposes, and construct facilities for managing concurrency some of which were hidden by the threading abstraction in the first place.

    5. Re:Why? by Anonymous Coward · · Score: 0

      This.

      I don't think the GP (or the +Insightful mods) have had to write large, multi-threaded applications.
      Or worse, had to add multi-threading to a pre-existing, single-threaded application. *shudder*

      That doesn't even get in to how hard QA and bug fixing are.
      "What do you mean you can only reproduce the behavior once out of 500 tries?!"

    6. Re:Why? by electrosoccertux · · Score: 1

      And more importantly, not all tasks CAN be parallelized.

      Why not just run two for twice the price?? Only, this one can be secret.

    7. Re:Why? by Tirno · · Score: 1

      Unless your code is entirely parallel, which is impossible in most cases, the serial portions will dominate performance as the number of cores increases. As such, better serial performance is critical to improving the scalability of even highly parallel workloads. If you want more information, this limitation is known as Amdahl's Law.

    8. Re:Why? by drinkypoo · · Score: 1

      Why this compromise? There's a huge need for developers to start thinking in terms of multicore CPUs. Offering them this solution is just postponing the inevitable. We need change now.

      Legacy applications. Anyway, we need better multicore support at the OS level, just like we need GPU rendering support at the OS level. Leaving it up to applications programmers to figure out either for themselves is a total failure.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Why? by Bengie · · Score: 1

      Because it's a pain in the ass and very hard for most coders.

      What we need is either a simple library for threading or a new language (like haskell) for auto-parallelization

      Parallel programming is like working with SQL. You have to structure your data in a way that's multi-thread friendly.

      I was in a discussion in another forum about Multi-threaded programmer. The general consensus was "If you make multi-threaded programmer easier for idiot programmers, you'll just be giving them a bigger gun to shoot themselves with".

      The issue with all of these new language tools is you can make an easy parallel for call on an array, only to find out you either made it slower or you sometimes get bad data because you still don't understand how it works. The new parallel language extensions are there to give programmers a shorthand version, but some programmers are going to think that these new addons magically make stuff run faster and you won't have to worry about anything.

      We just need fewer fail programmers.

  16. Question... by TheSHAD0W · · Score: 1

    Does Intel's architecture adjust its management scheme based on CPU temperature? It'd be nice if having a better heat sink or a cooling system would allow the system to run even faster.

    I've also been wondering why, given the new poly-core systems, we don't see a mix of CPU types in a system. Throwing a bunch of slower but less complex and therefore less expensive cores in with a few premium cores would result in a better balance, allowing the system to concentrate heavy-load apps on the faster CPUs while offloading less-intensive work onto the cheaper cores.

    1. Re:Question... by John+Hasler · · Score: 2, Insightful

      > I've also been wondering why, given the new poly-core systems, we
      > don't see a mix of CPU types in a system.

      How would the OS decide which process to assign to which core?

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    2. Re:Question... by sznupi · · Score: 1, Interesting

      Looking at history of CPU time to running time ratio for each process, or perhaps also what typically causes spikes of usage and moving process to faster core at that point? Plus central db of what to expect from specific processes.
      (I'm not saying it's necessarily a good idea; just that it could be not so hard, OS-wise)

      --
      One that hath name thou can not otter
    3. Re:Question... by sznupi · · Score: 1

      Though we do see a mix, in a different way, with GPGPU adoption.

      --
      One that hath name thou can not otter
    4. Re:Question... by TheSHAD0W · · Score: 2, Funny

      How about, every app that runs in the background or as a tray icon by default gets a cheesy core? :-P

  17. Redundant much? by Anonymous Coward · · Score: 0

    Wow - whoever wrote that article needs to go back to school. Did you know that the Intel solution is much more elegant because AMD tacked the Turbo core onto their K10 architecture they've been using for a while now?

  18. So buy a better cooler by Sycraft-fu · · Score: 1

    The stock Intel coolers are designed to be economical and meet the thermal requirements, not good.

    I use an Arctic Cooling Freezer 7 Pro. With my Q9550 I cannot make the fan spin up past the minimum, which is about 300rpm. The Intel board I use figures the CPU should maintain about a 20 degree thermal margin, meaning run 20 degrees below its rated max. If it is running hotter than that, the fan spins faster up to the max. If it is running cooler than that, the fan throttles back as low as the minimum. Idle, the CPU is around 40 degrees below the margin. If I crank up the processing, the heat will rise, but never high enough for the fan to speed up.

    In all cases, the fan is inaudible in the room.

    Also, you are aware that Intel makes more efficient, lower power CPU right? Have a desktop? Ok, instead of a Core i7 quad core, get a Core i3 dual core. It's made on the 32nm process and lacks some high end features (like VT-d and turbo boost) and runs rather low power. Has integrated low power graphics too, to further reduce whole system consumption. Just don't bitch that it isn't as powerful.

    For that matter, get a system with an Atom. Some of those are down near a watt in terms of usage, yet they still have the performance and features needed to run a modern OS and do things like surf the web.

    You can have low power efficient systems. You can have high power super systems. They are all available on the market today. You just can't have a system that uses very little energy and is a super performer.

  19. In layman's terms by digitalhermit · · Score: 4, Funny

    Just wanted to clarify some of the misconceptions about the Turbo Boost...

    The technology is fairly simple. At it's most level, we take the exhaust from the CPU fan and route it back into the intake of the system. If you're using Linux you can see the RPM increase by running 'top' (google Linux RPM for more information).

    The turbo itself is a fairly simple technology. As you're aware, we can use pipes to stream the outputs of different applications together. In the case of Linux, we pipe the stdout stream to the stdin (the intake) of the turbo (tr) which increases the speed and feeds it into a different application. For example, we can increase the throughput of dd as follows:

            dd if=/dev/zero | tr rpm | tee /proc/cpuinfo

    This will increase the CPU speed by feeding output from dd into the turbo (and increasing the rpm) and finally pumping it back into the CPU.

    On other platforms there are some proprietary solutions. For example, take the output of Adobe AIR to HyperV to PCSpeedup! then back into the processor.

    Hope this helps...

    1. Re:In layman's terms by toopok4k3 · · Score: 1

      Are you sure you don't need a filter to that pipeline? Surely /dev/zero can't be just clean 0's. All those 1 bits that get inside your cpu will eventually shorten the cpu's lifetime.

    2. Re:In layman's terms by Gothmolly · · Score: 1

      Hopefully people will not mod you offtopic.

      --
      I want to delete my account but Slashdot doesn't allow it.
    3. Re:In layman's terms by Anonymous Coward · · Score: 0

      The technology is fairly simple. At it's most level, we take the exhaust from the CPU fan and route it back into the intake of the system.

      FYI - That's not how a turbo works.
      A turbo is two turbines attached to a shaft.

      Turbine 1 is spun up using exhaust gas and the connecting shaft spins turbine 2 in order to compress & force 'fresh' air into the intake.

    4. Re:In layman's terms by jfernie · · Score: 1

      I heard they may use an enhanced version called Turbo Encabulator in next-generation CPUs.

      More info here:
      http://www.youtube.com/watch?v=MXW0bx_Ooq4

    5. Re:In layman's terms by Cytotoxic · · Score: 1

      The problem with this comes when you try to overclock. Then as the speed builds you end up in an overboost situation and that leads to detonation problems. To combat this you need a BOV (blow off valve) to bleed the extra bits from stdout so that proper levels of turbo boost are maintained. There are several after market BOV manufacturers available, but you have to integrate them with the turbo boost controller to get full control.

      Hope that helps....

  20. Marketeers from the 1980s called by Anonymous Coward · · Score: 0

    They want their "Turbo" bullshit back.

  21. "Your next build" - who builds PCs anymore? by Gothmolly · · Score: 1

    For $300 you can get a brand new Dell - who builds a PC anymore?

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:"Your next build" - who builds PCs anymore? by 0123456 · · Score: 4, Insightful

      For $300 you can get a brand new Dell - who builds a PC anymore?

      Someone who wants something better than a $300 Dell?

    2. Re:"Your next build" - who builds PCs anymore? by rwa2 · · Score: 1

      I bought one of those $400 laptops for my wife last year... 2.2Ghz dual core Toshiba Satellite with a fairly recent Intel 4000 integrated graphics chip.

      My upgraded 8-year old 2.2Ghz dual SMP Athlon XP-M with an AGP nVidia 6800GS still blows the doors off of it for gaming. Works great as long as the games don't require DX10 or 64-bit. And it actually didn't cost all that much since I waited to upgrade the CPUs, video, and RAM after they got cheap.

    3. Re:"Your next build" - who builds PCs anymore? by Cadallin · · Score: 1

      Um, people who read Slashdot? Or in other words, who are you and why are you posting from someone else's account?

    4. Re:"Your next build" - who builds PCs anymore? by GreatBunzinni · · Score: 1

      I built my desktop and I will build the next one when I finally upgrade. I build my desktop computers because I end up getting exactly what I want, the compatibility that I need and I end up getting it cheaper than anything Dell throws my way. For example, I've managed to build my desktop 4 years ago and not only it cost me 300 euros to build an Athlon X2 4000+ system with 2GB of RAM and with a 19'' monitor but it also gave me zero problems up to this day.

      Knowing that, I've took a peek at Dell's low bid offerings. You may be right, as it sells 270 dollar systems. Yet, they are measly intel celerons with intel graphics that come no monitor and whose life expectancy isn't exactly bragging material. That means that your 270 dollar desktop that you can buy from Dell is outperformed, outdated and outclassed by a computer assembled 4 years ago for less money.

      So, who buys a PC anymore? Those who know what they want, know what they are doing and know a ripoff when they see one, that's why.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
  22. Take advantage of what? by Yvan256 · · Score: 1

    take full advantage of multicore processers

    Too bad people don't use even a single core to correct their mistakes.

  23. Choosing between Intel and AMD? by Yvan256 · · Score: 0

    Interesting reading if you're choosing between Intel and AMD for your next build.

    Ah! I don't need to do such a thing! Apple decides for me*!

    * please Apple, put a Core 2 Quad** in the next Mac mini!

    ** Before you say "Core 2 Quad is old technology", compare the processing power, the power and heat dissipation requirements and the cost of a Core 2 Quad vs the Core i3, i5 and i7, even the mobile versions.

    1. Re:Choosing between Intel and AMD? by drspliff · · Score: 1

      The difference in heat dissipation requirements is negligible when it's a choice between 1cm or 2cm thick asbestos padding to avoid 3rd degree burns from your MacBook Pro.

    2. Re:Choosing between Intel and AMD? by Anonymous Coward · · Score: 0

      Raw GHz is useless, here is fair comparison in terms of processing power http://www.anandtech.com/show/2839/2 and here is one with respect to power consumption http://www.anandtech.com/show/2839/8

      From above charts, I would say i5,i7 own Core 2 Quad in terms of both processing power and power consumption.

    3. Re:Choosing between Intel and AMD? by Hurricane78 · · Score: 1

      You know that you can buy hardware elsewhere, and software too, right? Also you’re a smart grownup. You don’t need the Apple “’tardpadding”. ^^

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    4. Re:Choosing between Intel and AMD? by Yvan256 · · Score: 1

      There has to be Core 2 Quad with lower power consumption... the current Mac mini's power supply is 110W.

      I'm afraid the next Mac mini bump is going to be either another Core 2 Duo paired with the new nVidia 320M or a Core i3 with a crap intel GPU...

    5. Re:Choosing between Intel and AMD? by Anonymous Coward · · Score: 0

      Grownups who either use Apple or believe in any form of religion probably do need tardpadding in their daily lives.

  24. Because Intel knows their history by Animats · · Score: 3, Interesting

    When Intel came out with the Pentium Pro, they had a good 32-bit machine, and it ran UNIX and NT, in 32-bit mode, just fine. People bitched about its poor performance on 16-bit code; Intel had assumed that 16-bit code would have been replaced by 1995.

    Intel hasn't made that mistake again. They test heavily against obsolete software.

  25. Colotrim by jeaducy · · Score: 1

    Intel® Turbo Boost Technology is one of the many exciting new features that Intel has built into latest-generation Intel® microarchitecture. It automatically allows processor cores to run faster than the base operating frequency. Colotrim

  26. Turbo Boost by Santzes · · Score: 1

    I'm going with Turbo Boost for sure. With that my computer can jump over walls and lakes and stuff.

  27. Re:No turbine, no turbo by Khyber · · Score: 1

    "You will not find a turbine (ok, rotor with blades) in your CPU"

    Maybe not *IN* the CPU but the Delta that was on top of my heatsink was most certainly close to a turbine, right down to the ultra-high whining noise.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  28. Don't need to by Sycraft-fu · · Score: 1

    Turns out, you can figure out based on the kinds of programs yo run, how much cache you need to give good performance. With a sufficient amount of cache, you can have total effective throughput better than 90% of the throughput of just the cache itself. Thus more cache doesn't really get you anything. You find it is very much a logarithmic kind of function. With no cache, your performance is limited by the speed of the system memory. Just a little cache gives you a big increase. More makes sense, to a point (how much depends on the kind of programs you use) but it tapers off. So you double your cache and you get a 1% improvement. Not worth it.

  29. Also takes more complex hardware by Sycraft-fu · · Score: 1

    Adding more CPUs isn't as simple as just putting another socket on the board. There are real issues to be dealt with. That's one of the reasons you see such jumps in price for things. Making a CPU and chipset that deal with only a single processor is easier than multiple. Also at a certain point you end up having to add "glue" chips which deal with all the issues of all the multiple CPUs.

    Ok well that is all for symmetric multiprocessing, where all CPUs are equal. Add on a whole new layer of complexity if the CPUs are different and have different abilities and requirements.

  30. The article in one line by 1s44c · · Score: 1

    Turbo boost and turbo core over-clock cores in use up to a thermal limit.

    Hardly cutting edge stuff.

  31. I see only DOS can be benefactor here by dragisha · · Score: 1

    Because I still have to think of scenario in any modern OS where only one process wants CPU for itself.

    --
    http://opencm3.net, http://www.nongnu.org/gm2/
  32. correct me if i'm wrong, but by yanyan · · Score: 3, Interesting

    Correct me if i'm wrong, and maybe i'm missing something here, but i think it's possible to simulate this kind of functionality on Linux with a script. Cores 2 to N are taken offline (echo 0 > /sys/devices/system/cpu/cpu/offline), the "performance" governor is used for cpu0 (which causes it to run at full clock), then the script monitors usage of cpu0 and brings the other cores online as load on cpu0 goes up. When load goes down then the other cores can be taken offline again.

    1. Re:correct me if i'm wrong, but by josath · · Score: 1

      You're missing one very important point. Intel & AMD's tech allow the speed of the active cores to go ABOVE the standard processor speed. So say you have a 2.4GHz quad core CPU, yet with only 2 cores active it might run at 2.8GHz. With the older speedstep tech, you can only reduce the speed of cores, you cannot increase them over the rated speed (assuming you're not doing something risky like overclocking via BIOS or something of course)

      --
      sig? uhh, umm, ok
    2. Re:correct me if i'm wrong, but by StikyPad · · Score: 1

      You might be able to simulate it, but the real advance is that Intel developed high-k (very low leakage) transistors. A transistor that's "OFF" still has some amount of leakage current, thus power consumption and heat emission. In "older" transistors (and thus older processors), that leakage current was significant, at least when multiplied over millions of transistors. So even if you deactivate cores on the fly, you won't see nearly the power savings because your deactivated cores are still consuming a significant portion of your power (or thermal) budget. Likewise, if you were to overclock on the fly, you still wouldn't be able to achieve nearly the performance gains (not to mention that overclocking in the CPU by changing the clock multiplier is usually preferable to merely increasing the clock speed, which is the typical method these days).

      Some more info is available here:
      http://www.intel.com/technology/silicon/high-k.htm
      http://download.intel.com/design/processor/applnots/320354.pdf?iid=tech_tb+paper (White Paper, PDF).

  33. warning: patent problem by m.alessandrini · · Score: 0

    Michael Knight (or more probably Devon Miles) might sue Intel for the "turbo boost" concept.

  34. Re:No turbine, no turbo by Bert64 · · Score: 1
    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  35. Or, put another way by Colin+Smith · · Score: 1

    How to sell people lots and lots of cores but only have to actually deliver on one of them.

    Neat.

     

    --
    Deleted
  36. Re:WRI by Anonymous Coward · · Score: 0

    I don't get it.

  37. The Real Explanation by LennyP · · Score: 1
    First why we have symmetric multi-core chips.

    Problems:
    1) Intel hit a road block with being able to up the frequency it's processors (or anyone's processor's) could run at so marketing could no longer tout the next generation as being "faster."
    2) Intel needs to be able to continue providing excuses for continuing computer/chip sales; one needs to upgrade to run the latest version of the bloated and inefficient MS Windows.

    Solution:
    Give marketing new materials by putting multiple symmetric cores on a single chip. This can be done at negligible cost while providing a great marketing device for selling the "need" to upgrade one's system.

    Note that the SMP environment Intel came up with was NOT a solution for nor driven by any real life end users' problems. The only problem it solved was to provide marketing with a new sales campaign.

    As someone who has spent almost thirty years designing computer systems, there are two (among others) critical elements in designing any computer (or other) system. The first we all know is KISS or Keep it Simple, Stupid!. Along with the elegance of a simple solution, one also gets reliability and efficiency. No one that has every worked with an SMP system can claim it's simple; it may be the simplest solution for a given problem, but that does not make it simple.

    Second is the fact that most jobs everyone does every day with their computers does not need SMP. Further, to make matters much worse, the day to day tasks we use our computers for do not lend themselves to a SMP environment. Any analysis of what the typical user does with his/her computer will show that the task is most efficiently and reliably performed on a single core. This is why Intel, and now AMD, has included circuitry to essentially convert their SMP chips to single core. This is what allows XP's continued use successfully despite all the MS admonitions to upgrade; XP performs all the required tasks within the required time frame on a single core. This is why numerous benchmarks still show XP as outperforming Windows 7 for the vast majority of tasks performed by the home and business user.

    If we, especially Microsoft, bothered to design and implement software based upon the need to solve user's problems (and not simply to sell more software and hardware) we could go a long way to perform our computing tasks with ease and efficiency (both human and power) with a great deal more security than we have now. Microsoft, as a monopoly, has given little thought to giving the end-user the best computing experience as per the end-user's needs. Intel, and AMD, with the advent of the SMP chip have given Microsoft and other software developers the ability wreak havoc. Think, why else is the "latest" CPU innovation the ability to cut back code execution from across multiple cores to a single core?

    1. Re:The Real Explanation by Bengie · · Score: 1

      #1. is correct, but #2 is not.

      Even lowly i5 cpu can boot Win7 is under 10 seconds with an SSD and can run any game and decode any video with ease.

      Most people may not need a quad core, but even a dual core makes your OS experience seem much more responsive.

      AMD and Intel do not "convert" their chips into single cores. It's just logical that if you're loading the whole cpu, why not make one part faster. No point in wasting electricity with 3 of of your cores being powered on. XP is great at single threads and does not scale almost at all with SMP. Single threaded programming has a HUGE diminishing return on ROI for transistor count. Better off making a a whole separate core.

      What it comes down to is there are only a few ways to increase single threaded speed.
      #1. Out-of-Order Execution. This takes quite a bit of transistors and is only as good as your instruction windows size. You cannot change the order of many instructions. Also, the larger your instruction window, the slower your chip has to run as it needs more time to check all of the instructions first.

      #2. Increase register count. More registers means fewer moves and fewer memory load/stores (for tight loops anyway), but this also has diminishing returns because you can only use so many registers at a time with your instructions and eventually you have to move on anyway and load/store more data from memory which means after a few extra registers, your bottleneck moves back to memory.

      #3. SIMD. MMX/SSE/ETC are all great at crunching matricies of data and sometimes using special instructions that effectively perform many general isntructions in fewer steps than using those general purpose instructions. SIMD itself is also exclusinvely useful for Graphics/Math/Science/Games and near useless for everyday computing.

      #4. MHZ. And who could forget the P4(aka space heater). Seems increasing clock speed takes a a huge amount more power as it goes up as you need to use more and more power to quickly oscilate your clock. They also found more interesting problems with higher clock speeds. Seems electricity can only travel so fast and they had to add extra steps in the pipeline to give the signals enough time to propigate accross the chip.

      #5. Pre-fetching and/or more cache. You can add some instructions to help prefetch data but this has limited use as it consumes at least a cycle where you could have done real work and you don't always know yourn next memory address to make use of prefetch. More cache has the lovely problem of adding more latency which would make pre-fetching more useful but at a heavy cost of affecting everything else.

      #6. anything else I forgot about.

      In the end you have two things. 1) single threaded performance about hit a brick wall and was going almost no where. 2) If you don't go SMP, someone else will and you'll die a corprate death for not advancing.

    2. Re:The Real Explanation by LennyP · · Score: 1
      Hi,

      Regarding my #2 being wrong, there is nothing in your reply that rebuts it. Intel needs to be able to continue providing excuses for continuing computer/chip sales, that is capitalism and there's nothing wrong with it (except from an environmental view!) One needs to upgrade to run the latest version of the bloated and inefficient MS Windows.

      "Even lowly i5 CPU can boot Win7 is under 10 seconds with an SSD and can run any game and decode any video with ease." Right, if it's a clean install. So you agree with me. Without hardware compensating for the additional bloat we have a turkey besides the number of cores on a CPU does not make any great affect on boot time. As to running any game or encode/decode video, these are task best left to your video card not the CPU -- and the last time I looked, gamers were still overclocking because they had to for improved gaming.

      "Most people may not need a quad core, but even a dual core makes your OS experience seem much more responsive." Very few, if any people need a quad core; absolutely agree. And for those that do, what software out there efficiently utilizes any SMP based machine? Nothing I know of for the typical user. As to dual core, as per your previous statement, an SSD is what really would make a difference -- not dual core. Besides, again, what software make efficient use of an SMP dual core?

      "AMD and Intel do not "convert" their chips into single cores." True, but it's a pretty good layman's example of what is happening; some cores are shutdown with power boosts to the remaining core(s) increasing their speed. Any way you look at it, you just bought cores that are not needed and can slow down your system.

      "It's just logical that if you're loading the whole CPU, why not make one part faster." Actually that is exactly what Intel used to do till some thermal barriers were hit forcing Intel to move to multi-core. Logically, and in the hardware/software world I grew up in -- Intel and embedded -- the first thing you do is get rid of the inefficiencies so the system can handle the load (as in proper design) Logically, as well, if by speeding up CPU you can make the system more efficient why have more cores in the first place? Doesn't it strike you as odd that after all the hype about multi-core, the latest and greatest is the ability to not use multi-core? There's not much software out there that uses multi-core, efficiently or otherwise. Again, as you stated, "Most people may not need a quad core"

      All the discussion about how to increase throughput for a single thread is pretty much not relevant. I will state that the best ways to increase throughput for a single thread are by optimizing architecture, design (eg algorithm chosen) and implementation. Unfortunately in the PC world (thank you MS) engineering is more often hacking/programming than real engineering. (See TGMLC.)

      "In the end you have two things. 1) single threaded performance about hit a brick wall and was going almost no where. 2) If you don't go SMP, someone else will and you'll die a corprate death for not advancing." 1) single threaded performance did not hit a brick wall nor was it any where near hitting a brick wall -- I/O bound was/is a much greater problem. The CPU thermal barriers to increased speed have nothing to do with the level of parallelism of any program, process, or task. 2) Maybe. In the server world the quest is to find the best all around solution which may or may not be SMP on a single core. In the end user world, it a question of marketing and, right now, marketing is pushing SMP on a single chip. (See TGMLC)

      Finally, why add complexity where none is needed. Many of the difficulties of parallel programming are quite well documented. Here's yet another: http://arstechnica.com/security/news/2010/05/multicore-cpus-move-attack-from-theoretical-to-practical.ars

  38. AMD on HP & Dell? by red+crab · · Score: 1

    I am in lookout for an AMD notebook since last two weeks. Was surprised to see HP and Dell aren't offering AMD on any of their models now . Only Lenovo and Acer have some AMD offerings. Not sure about Dell but HP did have AMD models in Compaq series in the past. Its bad to see the two major PC makers unfairly promoting the bigger brand.

  39. um Itanium? by Anonymous Coward · · Score: 0

    seems to me to be exactly the same mistake