First Haswell performance benchmarks hit the web


Recommended Posts

I'm still on a q9400, but if i do an upgrade this year, it will probably be hanswell ... i'm waiting to see the the price points.

I'm on a Q6600 (which my mom will get when I upgrade to i5-3570K) - unless you run niche applications that make heavy usage of hyperthreading, I would stick to Ivy Bridge, not Haswell.

1, First off, Haswell will require a new motherboard, new chipset, and a different CPU socket than Sandy Bridge/Ivy Bridge - all of which are pricey on launch. (The only reason that wasn't the case for Ivy Bridge is that it used the same socket, and, by and large, the same chipsets as Sandy Bridge; further what new chipsets that WERE launched simultaneously with Ivy also supportewd Sandy.)

2. Simultaneously, Haswell's launch WILL lead to price cuts - not just as those that DO upgrade sell existing hardware, but as existing hardware (CPUs and motherboards) take it on the chin price-wise. (Look at what happened to Z68 motherboards when Z77 launched - immediate price cuts of thirty percent, at minimum.)

3. Going by the initial benchmarks, Haswell will target the high end of portable computing and servers more so than general computing - especially given the high prices of Haswell at launch and price cuts hitting Ivy.

Save your money - stick to Ivy Bridge.

Not much of an increase. Should I stick with getting a 3770K for my new build then?

I tend to agree with what PGHammer has said above me (if no one else posts before I do :p)

For most people, Ivy Bridge will likely not be bottlenecking most people for a while, and that includes gamers. I myself am on Sandy Bridge and I don't intend to upgrade at least until next year at the earliest, when (I believe, correct me if I'm wrong) DDR4 RAM will be officially supported by Skylake.

You will also save a decent amount of money as well that you can use to spend on other components of your PC.

3. Going by the initial benchmarks, Haswell will target the high end of portable computing and servers more so than general computing - especially given the high prices of Haswell at launch and price cuts hitting Ivy.

Save your money - stick to Ivy Bridge.

http://en.wikipedia....croarchitecture)

Now that I've read that, there's no way in hell I'd pick Ivy over Haswell. I don't know about the processors but the motherboards should be considerably cheaper.

No, we shoudl all still be using 90nm because it's so horribly cost effective.

I think you don't get my point: just because the may be shrinking the PCH - note that that's not even confirmed! - that doesn't mean that your hardware will get cheaper! Matter of fact: Building a 22nm fab is horribly expensive (see Rock's Law) and Intel has to re-finance the fab...

I think you don't get my point: just because the may be shrinking the PCH - note that that's not even confirmed! - that doesn't mean that your hardware will get cheaper! Matter of fact: Building a 22nm fab is horribly expensive (see Rock's Law) and Intel has to re-finance the fab...

It said 32nm, and they're already past that (note Haswell is 22nm)

at any rate, expensive motherboards are what annoys me about Intel systems so I hope it is true.

The bigger question is what is AMD going to do?

AMD keep releasing eight-cores processors with horrible per-core performance. I would rather buy a quad-core processor with decent per-core performance.

Temash, Kabini, and Kaveri are all due for release this year, and should be interesting. I don't know if they'll be able to compete or not beyond the tablets but I definately hope so.

http://www.tomshardw...mance,3461.html

The review unfortunately says nothing about power consumption, heat or overclocking, but it does look like Haswell is another solid incremental upgrade over the previous generation. Software recompiled to take advantage of the new AVX2 and TSX instructions should see much larger gains.

According to the information there, no TSX in the unlocked K-models. Which means Intel are crippling the performance models deliberately.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!