Recommended Posts

Intel didn't really cause mixed feelings among its followers the same way AMD did, but it still offered a reason for them to be less than enthusiastic by not being as enthusiastic as them, so to speak.

Intel recently 'disappointed' the more enthusiastic of its followers by revealing that its first Sandy Bridge-CPU would not have eight cores.

That is to say, not all eight of them would be enabled and, instead, 'only' six would be up and ready to breeze through even the most hardcore of games and applications.

A short list of reasons was compiled in order to explain to those hardcore overclockers and gamers why this is going to happen.

The TDP (thermal design power) is the most obvious of them, since the E chips are very big beasts (relatively speaking) and have a lot of cache memory.

Desktops nowadays try to stay at 120W or under, while an eight-core chip, with a clock speed higher than 3 GHz (to justify the upgrade form old CPUs to new ones) would demand about 150W.

The other major reason is how operating systems don't really know what to do with chips that have so many cores (they can barely put six of them to work, let alone eight).

In other words, Intel is making the same argument AMD used to assure prospective buyers that the FX Bulldozer chips willgain performance when Windows 8 appears.

All in all, the first Sandy Bridge-E CPUs will, in the end, have 'only' six cores because the company wouldn't have been able to jam more than that number, working at 3.3 GHz, into the 130W limit.

After all, since enthusiasts won't really be susceptible to the wiles of eight-core units if said chips don't have at least 3 GHz from the get go.

Intel should get around to enabling all eight cores at the next CPU stepping (with 20 MB L3 cache memory instead of 15).

source:

http://news.softpedia.com/news/First-Intel-Sandy-Bridge-E-CPU-Has-Only-6-Cores-Enthusiasts-Disapprove-228018.shtml

They should really say "Windows doesn't know how to use more cores" because Linux and BSD definitely can, and properly for that matter (as well as OS X).

*scratches head* yet Windows 7 was to take full advantage of multithreading it was one of the "features" of Windows 7's environment... so that whole thing makes no sense... because I can run 8 cores perfectly fine at full speed in windows server 2008 r2...

  • Like 3

Completely understand where they're coming from on this one. The cores have to be utilized for them to be useful and they have to each have to match current processors in speed. If they're not fully utilized (and for the most part they won't be yet.) they're superfluous, and if each core isn't as fast as current quads (or six-core processors) then there is absolutely no reason to upgrade to them as you won't see any benefit at all until support for 8 cores is common. Granted there are some applications that will take advantage of 8 cores, but not that many, and even fewer that the average person uses. On the gaming front it took forever and a day to get a decent number of them supporting 4-cores, I'm hoping that support for 8 won't be such a major headache.

My guess is they just haven't perfected the manufacturing process yet, and their batches routinely have 1-2 defective cores, so they're just salvaging them and marketing them like AMD with the tri-core cpu's. The reasons they give don't hold any weight IMO. If the next stepping will have 8 cores, and the same clock speed they will still consume 150W eventually. Surely, the performance would not be worse with 8 cores vs. 6 cores even if windows 7 cannot manage threads efficiently.

They have 8 core XEON's this is just them not feeling the heat from AMD. No reason to release an 8 Core CPU when they have no competition. Don't you find it suspect they waited a mere 3 days after the Bulldozer benches to release these statements when they could have said this months ago when they finalised the specifications and pricing of the three chips?

Had Bulldozer knocked the socks off Intel's 6 core Sandy Bridge E, they would have most definitely brought an 8 Core to market. No question.

  • Like 1

My guess is they just haven't perfected the manufacturing process yet, and their batches routinely have 1-2 defective cores, so they're just salvaging them and marketing them like AMD with the tri-core cpu's. The reasons they give don't hold any weight IMO. If the next stepping will have 8 cores, and the same clock speed they will still consume 150W eventually. Surely, the performance would not be worse with 8 cores vs. 6 cores even if windows 7 cannot manage threads efficiently.

8 Core Xeon's have been out for well over a year, Intel has it down pretty good imho...

Look up the Xeon 7500/Xeon E7-8830

My guess is they just haven't perfected the manufacturing process yet, and their batches routinely have 1-2 defective cores, so they're just salvaging them and marketing them like AMD with the tri-core cpu's. The reasons they give don't hold any weight IMO. If the next stepping will have 8 cores, and the same clock speed they will still consume 150W eventually. Surely, the performance would not be worse with 8 cores vs. 6 cores even if windows 7 cannot manage threads efficiently.

I know they are having trouble with yields on Sandy Bridge right now, so I'd bet on this.

8 Core Xeon's have been out for well over a year, Intel has it down pretty good imho...

Look up the Xeon 7500/Xeon E7-8830

Just because one type of chip can be manufactured with 8-cores does not mean a newer architecture automatically can be.

8 Core Xeon's have been out for well over a year, Intel has it down pretty good imho...

Look up the Xeon 7500/Xeon E7-8830

I know. That's what I said. Intel have 8 Core XEONS. I've personally had access to the X7560. I use two Six core L5640's personally. The 8 core processors are more than 4x as much as the L5640.

And this is also due to a lack of competition. AMD's 12 Core Opterons do not even beat Intels Six core processors let alone the 8 Core XEON chips.

I know. That's what I said. Intel have 8 Core XEONS. I've personally had access to the X7560. I use two Six core L5640's personally. The 8 core processors are more than 4x as much as the L5640.

And this is also due to a lack of competition. AMD's 12 Core Opterons do not even beat Intels Six core processors let alone the 8 Core XEON chips.

Intel has 10 core Xeons out also. :)

They have 8 core XEON's this is just them not feeling the heat from AMD. No reason to release an 8 Core CPU when they have no competition. Don't you find it suspect they waited a mere 3 days after the Bulldozer benches to release these statements when they could have said this months ago when they finalised the specifications and pricing of the three chips?

Had Bulldozer knocked the socks off Intel's 6 core Sandy Bridge E, they would have most definitely brought an 8 Core to market. No question.

Agreed, took the words out of my mouth. This is what happens when you nearest competitor can't compete. Come on AMD step up your game.

People still don't get that to benefit from all the cores, you have to write specifically coded apps to take advantage of those cores using parallel programming libraries and compilers. Regular apps just won't automagically benefit from increased cores. Yes the scheduler in Windows 7 has some optimizations for multiple cores to ensure fairer scheduling. But even in this test for example, XP outperforms Windows 7 on dual and quad cores. Only when it cores increase to 8 or more, Windows 7 leaps ahead.

these 6 core cpus most likely are the ones that don't meet x8 that are used in the xeons or some i7 xtream to be released later. This is fairly common in the cpu world. Unless you buy the top of the line you are buying something that is defective so to speak.

Regular apps just won't automagically benefit from increased cores.

If you have ever used Foobar2000 or dBpowerAMP to encode music you will know this is not quite true. The more cores you have, the more copies of Lame.exe or NeroAACEnc.exe you can run simultaneously. Then you have multi-process apps like Google Chrome...

pXEGA.png

these 6 core cpus most likely are the ones that don't meet x8 that are used in the xeons or some i7 xtream to be released later. This is fairly common in the cpu world. Unless you buy the top of the line you are buying something that is defective so to speak.

I would definitely agree with this, but the article only says Sandy Bridge E, which includes the Xeons as well. I'm curious if this limitation will exist on the early Xeons as well. I know the ES chips are 8 core, but I have heard they are still getting pretty poor yields out of the chips right now.

If you have ever used Foobar2000 or dBpowerAMP to encode music you will know this is not quite true. The more cores you have, the more copies of Lame.exe or NeroAACEnc.exe you can run simultaneously. Then you have multi-process apps like Google Chrome...

That's because apps like encoding tools are usually almost always multi-core optimized by their developers, they are not regular apps. :)

This topic is now closed to further replies.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      530
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!