The Intel Core i7 860 Review

by Anand Lal Shimpi on September 18, 2009 12:00 AM EST

DivX 8.5.3 with Xmpeg 5.0.3

Our DivX test is the same DivX / XMpeg 5.03 test we've run for the past few years now, the 1080p source file is encoded using the unconstrained DivX profile, quality/performance is set balanced at 5 and enhanced multithreading is enabled:

DivX 6.8.5 w/ Xmpeg 5.0.3 - MPEG-2 to DivX Transcode

Lynnfield inches towards the crown with the 860; it's closer to the 870 than the Core i5 750, and that's to be expected. The biggest gains here are due to Hyper Threading, the clock speed is just icing on the cake.

x264 HD Video Encoding Performance

Graysky's x264 HD test uses the publicly available x264 codec (open source implementation of H.264) to encode a 4Mbps 720p MPEG-2 source. The focus here is on quality rather than speed, thus the benchmark uses a 2-pass encode and reports the average frame rate in each pass.

x264 HD Encode Benchmark - 720p MPEG-2 to x264 Transcode

The Core i7 860 continues to do better than the i7 920, even if by only a small margin. As expected, it's closer to the 870 than it is to the i5 750 thanks to Hyper Threading.

x264 HD Encode Benchmark - 720p MPEG-2 to x264 Transcode

 

Windows Media Encoder 9 x64 Advanced Profile

In order to be codec agnostic we've got a Windows Media Encoder benchmark looking at the same sort of thing we've been doing in the DivX and x264 tests, but using WME instead.

Windows Media Encoder 9 x64 - Advanced Profile Transcode

The race is close here, there's only a 2 second difference between the Core i7 870 and the Core i5 750. The 860 lands closer to the 750 this time.

Adobe Photoshop CS4 Performance 3D Rendering Performance
Comments Locked

121 Comments

View All Comments

  • strikeback03 - Monday, September 21, 2009 - link

    In previous tests Anand has used the fastest validated speed for each platform, so 1066 for Bloomfield and 1333 for Lynnfield. Not that it probably makes much difference in anything but synthetic benchmarks.
  • Scheme - Saturday, September 19, 2009 - link

    Woah, did you forget to take your ritalin last night?
  • mesiah - Saturday, September 19, 2009 - link

    Anand, can't you ban this guy? You have to be tired of watching him come on here and verbally assault any person he doesn't agree with, including yourself. Do everyone a favor and toss him to the curb.
  • jonup - Sunday, September 20, 2009 - link

    Noooo! This would be too cruel. We need a joker to make us laugh from time to time.
  • tim851 - Saturday, September 19, 2009 - link

    Let me guess, you have an i7 920...?

    Of course the 860 ran at higher clock speeds, why would Anand underclock it? It was compared to the 920 because they share the same price point. That is until you add the motherboard, then the i7 is like 100$ more expensive.

    And Anand summed it up nicely: the 1366 platform is now for people who need hexa-cores someday or who think SLI/Crossfire is reasonable.

    Oh, and if the P55 Platform is "braindamaged", then apparently all major tech sites are in on the conspiracy.
  • jordanclock - Saturday, September 19, 2009 - link

    What do you mean by "inferior memory?"

    And of course the 860 was running at a higher clock rate: That's how it is designed to run. Even without Turbo.
  • TA152H - Saturday, September 19, 2009 - link

    I don't have a problem with the 860 running at higher clock speeds, but if the architecture were better, it would never lose to a processor running at lower clock speeds.

    In short, the architecture is not clearly better. It's worse, the margin is the only thing worth discussing.
  • TA152H - Saturday, September 19, 2009 - link

    I should have said, i7 920 still outperformed it in a few benchmarks.

    Pity there isn't an edit.
  • JumpingJack - Saturday, September 19, 2009 - link

    The basic architecture of Lynnfield is the same as Bloomfield. The differences are the topology of the platform (PCI on die instead of in the chipset, 2 mem controllers instead of 3, no QPI in Lynnfield). The cores are exactly the same, the cache is exactly the same.
  • jordanclock - Saturday, September 19, 2009 - link

    I have yet to see any real world scenarios where triple channel memory "really shines." The inclusion or exclusion of a triple channel set up would account for variations of about 1% either way. In other words, less than the margin of error.

Log in

Don't have an account? Sign up now