Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by janrinok on Tuesday August 27 2019, @05:49PM   Printer-friendly
from the apples-and-oranges? dept.

Over at www.semiaccurate.com they are discussing - in unfavourable terms - the launch by Intel of the 'Comet Lake' series of CPUs:

Intel LogoLast week Intel launched their '10th Gen' CPUs, a self-inflicted wound that shouldn't have been released. If you think SemiAccurate is being a bit harsh here, ask yourself why Intel birthed this debacle in the first place.

[...]

But performance is why we are mocking Intel over this ‘family’. The company split out the Ice and Comet briefings so as to minimize comparisons and uncomfortable questions between the two. As we pointed out in our earlier article on Ice there were vague comparisons between the two ranges but no actual data. Intel even unethically hid the SKUs they were testing.

This time was more of the same, absolutely zero charts comparing this ‘generation’ to the last, or even to itself. All we got was a slide saying, “up to 16% better overall performance vs. previous gen”. That may sound great but, err, 6 cores vs 4 should get one a 50% higher performance or at least something closer to 50% than 0%, right? Don’t forget the faster memory on the new Comet devices which should get you a big chunk of that 16% alone. That level of sleaze is expected but we didn’t expect Intel to be outright unethical. Again. Actually we kinda did but we honestly hoped they wouldn’t do it again.

Yup that 16% max increase when going from a 6C i7-10710U to a 4C i7-8565U was bad. The fact that they compared a 25W 10710U to a 15W 8565U and buried that fact in the fine print is unacceptable. We once again call for the idiots responsible to be fired, not that Intel will do anything, it seems this sort of behavior has become acceptable at big blue. It still isn’t right.

Read the story and see if you agree.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Informative) by boltronics on Wednesday August 28 2019, @02:40AM (2 children)

    by boltronics (580) on Wednesday August 28 2019, @02:40AM (#886604) Homepage Journal

    I have an i7 6700k Skylake, and yeah I had a ton of issues when I first got it. memtest86+ was refusing to pass in multi-processing mode (apparently the CPU is incompatible with the test?? - I think this is still a thing) and the integrated GPU goes nuts when the RAM was running at its rated 3200MHz setting - took quite a lot of time to figure that one out, but is apparently a common issue with them. I put in an AMD Fury X which gave me no issues.

    Then there were some compiler bugs at launch that were causing builds to fail for months post launch. Then there was all the security issues... and I was very disappointed by how few drives it would support - in my case I had 2x M.2 and 3x SATA max since adding the M.2 drives causes all other SATA ports to be disabled - and most motherboards supported much less! Quite a bad experience overall. I look forward to the next time I upgrade my desktop, where picking AMD will be a no-brainer.

    --
    It's GNU/Linux dammit!
    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Informative=1, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 2) by JoeMerchant on Wednesday August 28 2019, @12:55PM

    by JoeMerchant (3937) on Wednesday August 28 2019, @12:55PM (#886753)

    the integrated GPU goes nuts when the RAM was running at its rated 3200MHz setting

    Thanks for the thought... might try some BIOS detuning to see if I can get stable video output...

    --
    🌻🌻 [google.com]
  • (Score: 2) by JoeMerchant on Wednesday August 28 2019, @12:58PM

    by JoeMerchant (3937) on Wednesday August 28 2019, @12:58PM (#886756)

    compiler bugs

    When Intel comes out with a new "compatible" chip and gcc fails on it, who really caused the bug? Did icc even work properly? https://software.intel.com/en-us/c-compilers [intel.com]

    --
    🌻🌻 [google.com]