By: --- (---.delete@this.redheron.com), January 27, 2023 10:31 am
Room: Moderated Discussions
Anne O. Nymous (not.delete@this.real.address) on January 27, 2023 12:09 am wrote:
> Chris G (chrisg.delete@this.chrisg.com) on January 26, 2023 5:02 pm wrote:
> > I thought this quote from the NY Times article was interesting: “She also determined that Intel had
> > scheduled more products than its engineers and customers could easily handle. So she streamlined that
> > product road map, including pushing back a successor to Sapphire Rapids to 2024 from 2023.”
> >
> > In other words, Xeon Emerald Rapids is also delayed again. Emerald Rapids is just Sapphire Rapids with
> > some more errata fixed, a 17% increase in DRAM bandwidth and a 25% increase in intersocket bandwidth
> > on the same process technology. It could be that the complexity of x86 and the hairball of their numerous
> > instruction set extensions is just too much for anyone to deal with. I would also guess a big part of
> > Intel’s problem is poor management. Andy Grove was probably the best technology manager of all time
> > but that was a long time ago. Now the type of innovation
> > we get from Intel is renaming the process technology
> > from Intel 4 to Intel 3 because a name with a smaller number must surely be better.
>
> You know that Pat Gelsinger became CEO of intel just ~ 2 years ago? It takes time to change things,
> so maybe give the gentleman a bit more time to pull things around (well possible he might fail
> given the "institutional inertia" of a behemoth company like intel, but he might prevail, but we
> only know after giving the whole exercise enough time to play out one way or the other).
>
> Now, it looks pretty clear that intel was resting on its laurels for too long and
> the whole 10nm process cluster-fsck certainly did not help, but not sure whether
> all is doom and gloom, it is still a pretty rich and resourceful company...
Outsiders obviously have to work with limited data; we can't prove anything, we can just point to patterns and say what they suggest to us.
Having said that, I compared Pat with Steve Job's return to Apple, or even Satya's first two years. Both made it clear in their first year that it was no longer business as usual, that things had to be shaken up and changed.
Conversely I don't see Pat as doing anything similar. Steve, for example, dealt with complexity (of a different sort, sure) by dramatically pruning the product line. But Pat has done nothing similar. Intel differentiators (whether AVX512 or accelerators) are used as a market segmentation mechanism, not as a way to grow the ecosystem.
IMHO the fundamental problem with Intel is that engineers are not in charge. Finance controls one set of decisions, marketing controls another. Steve or Satya would have dealt with this by dramatic changes in those core areas; but Pat retains the dividend, in spite of everything, and retaining the marketing control (engineer effort spread over finely differentiated product segmentation, far too much making promises and setting schedules before it's known what is possible). Compare how Intel and AMD comport themselves in this respect.
It's easy to mock Intel or complain for tribal reasons. The problem is, it's just as easy to do so for good, grounded, data-based reasons.
> Chris G (chrisg.delete@this.chrisg.com) on January 26, 2023 5:02 pm wrote:
> > I thought this quote from the NY Times article was interesting: “She also determined that Intel had
> > scheduled more products than its engineers and customers could easily handle. So she streamlined that
> > product road map, including pushing back a successor to Sapphire Rapids to 2024 from 2023.”
> >
> > In other words, Xeon Emerald Rapids is also delayed again. Emerald Rapids is just Sapphire Rapids with
> > some more errata fixed, a 17% increase in DRAM bandwidth and a 25% increase in intersocket bandwidth
> > on the same process technology. It could be that the complexity of x86 and the hairball of their numerous
> > instruction set extensions is just too much for anyone to deal with. I would also guess a big part of
> > Intel’s problem is poor management. Andy Grove was probably the best technology manager of all time
> > but that was a long time ago. Now the type of innovation
> > we get from Intel is renaming the process technology
> > from Intel 4 to Intel 3 because a name with a smaller number must surely be better.
>
> You know that Pat Gelsinger became CEO of intel just ~ 2 years ago? It takes time to change things,
> so maybe give the gentleman a bit more time to pull things around (well possible he might fail
> given the "institutional inertia" of a behemoth company like intel, but he might prevail, but we
> only know after giving the whole exercise enough time to play out one way or the other).
>
> Now, it looks pretty clear that intel was resting on its laurels for too long and
> the whole 10nm process cluster-fsck certainly did not help, but not sure whether
> all is doom and gloom, it is still a pretty rich and resourceful company...
Outsiders obviously have to work with limited data; we can't prove anything, we can just point to patterns and say what they suggest to us.
Having said that, I compared Pat with Steve Job's return to Apple, or even Satya's first two years. Both made it clear in their first year that it was no longer business as usual, that things had to be shaken up and changed.
Conversely I don't see Pat as doing anything similar. Steve, for example, dealt with complexity (of a different sort, sure) by dramatically pruning the product line. But Pat has done nothing similar. Intel differentiators (whether AVX512 or accelerators) are used as a market segmentation mechanism, not as a way to grow the ecosystem.
IMHO the fundamental problem with Intel is that engineers are not in charge. Finance controls one set of decisions, marketing controls another. Steve or Satya would have dealt with this by dramatic changes in those core areas; but Pat retains the dividend, in spite of everything, and retaining the marketing control (engineer effort spread over finely differentiated product segmentation, far too much making promises and setting schedules before it's known what is possible). Compare how Intel and AMD comport themselves in this respect.
It's easy to mock Intel or complain for tribal reasons. The problem is, it's just as easy to do so for good, grounded, data-based reasons.
Topic | Posted By | Date |
---|---|---|
NYT on SPR | --- | 2023/01/26 10:37 AM |
NYT on SPR | Chris G | 2023/01/26 06:02 PM |
NYT on SPR | me | 2023/01/26 07:44 PM |
NYT on SPR | Anne O. Nymous | 2023/01/27 01:09 AM |
NYT on SPR | Michael S | 2023/01/27 03:22 AM |
NYT on SPR | --- | 2023/01/27 10:31 AM |
Pat has been trimming the Intel product portfolio | Mark Roulo | 2023/01/27 01:29 PM |
NYT on SPR | James | 2023/01/27 02:00 PM |
NYT on SPR | Adrian | 2023/01/28 03:55 AM |
NYT on SPR | anonymou5 | 2023/01/28 04:03 AM |
NYT on SPR | Adrian | 2023/01/28 04:14 AM |
NYT on SPR | Groo | 2023/01/29 09:50 AM |
NYT on SPR | Groo | 2023/01/29 09:46 AM |
NYT on SPR | Brendan | 2023/01/29 01:00 PM |
NYT on SPR | Anon4 | 2023/01/29 04:06 PM |
NYT on SPR | Brendan | 2023/01/29 07:03 PM |
NYT on SPR | Groo | 2023/01/30 07:09 AM |
NYT on SPR | Groo | 2023/01/29 09:39 AM |
NYT on SPR | AnonSoft | 2023/01/30 11:01 AM |
NYT on SPR | hobold | 2023/01/30 12:39 PM |
NYT on SPR | AnonSoft | 2023/01/30 05:34 PM |
NYT on SPR | hobold | 2023/01/31 04:40 AM |
NYT on SPR | Jukka Larja | 2023/01/31 07:13 AM |
Heterogeneous CPU Cores With OpenMP | Mark Heath | 2023/02/01 04:45 AM |
Heterogeneous CPU Cores With OpenMP | Freddie | 2023/02/01 05:05 AM |
Heterogeneous CPU Cores With OpenMP | Mark Heath | 2023/02/01 06:42 AM |
Heterogeneous CPU Cores With OpenMP | Freddie | 2023/02/01 09:54 AM |
Heterogeneous CPU Cores With OpenMP | Mark Heath | 2023/02/01 04:45 PM |
Heterogeneous CPU Cores With OpenMP | —- | 2023/02/02 04:35 PM |
Heterogeneous CPU Cores With OpenMP | Freddie | 2023/02/02 04:39 PM |
Heterogeneous CPU Cores With OpenMP | --- | 2023/02/03 12:15 PM |
Heterogeneous CPU Cores With OpenMP | Freddie | 2023/02/03 03:46 PM |
Heterogeneous CPU Cores With OpenMP | Anne O. Nymous | 2023/02/03 12:57 AM |
Heterogeneous CPU Cores With OpenMP | --- | 2023/02/03 12:35 PM |
Heterogeneous CPU Cores With OpenMP | Anne O. Nymous | 2023/02/03 01:35 PM |
different big/little split.. | Heikki Kultala | 2023/02/03 02:33 PM |
Heterogeneous CPU Cores With OpenMP | Paul H | 2023/02/03 06:51 PM |
Heterogeneous CPU Cores With OpenMP | Jukka Larja | 2023/02/01 06:24 AM |
When heavily loaded, Threads run about equally fast on E-cores than P-cores | Heikki Kultala | 2023/02/01 02:08 PM |
NYT on SPR | Chester | 2023/01/27 09:30 AM |
use archive.org | anon | 2023/01/27 06:08 PM |
Bypassing paywalls | Doug S | 2023/01/28 02:05 PM |
NYT on SPR | Chris G | 2023/01/27 06:54 PM |
Intel On Demand | Chris G | 2023/01/28 04:24 AM |
Intel On Demand | me | 2023/01/28 06:24 AM |
Intel On Demand | Groo | 2023/01/29 09:53 AM |
Intel On Demand | rwessel | 2023/01/28 09:41 AM |
Intel On Demand | --- | 2023/01/28 11:37 AM |
Anit-waste bias | Paul A. Clayton | 2023/01/28 07:57 PM |
Intel On Demand | Groo | 2023/01/29 09:58 AM |
Intel On Demand | Andrey | 2023/01/30 05:04 PM |
Intel On Demand | blaine | 2023/01/28 03:07 PM |
Intel On Demand | me | 2023/01/28 03:25 PM |
Intel On Demand | me | 2023/01/28 03:33 PM |
Intel On Demand | Chris G | 2023/01/28 07:06 PM |
Intel On Demand | me | 2023/01/28 07:43 PM |
Intel On Demand - Validation, certification? | Björn Ragnar Björnsson | 2023/01/28 10:41 PM |
Intel On Demand - Validation, certification? | anonymou5 | 2023/01/29 02:49 AM |
Sapphire Rapids crippleware is a naked money grab | Chris G | 2023/01/29 04:44 AM |
Intel On Demand - Validation, certification? | Groo | 2023/01/29 10:05 AM |
Intel On Demand - Validation, certification? | AnotherAnonymousEngineer | 2023/01/29 10:33 AM |
Intel On Demand - Validation, certification? | Groo | 2023/01/29 11:16 AM |
Intel On Demand - Validation, certification? | dmcq | 2023/01/29 04:32 PM |
Intel On Demand - Validation, certification? | Brendan | 2023/01/29 08:01 PM |
Intel On Demand - Validation, certification? | Groo | 2023/01/30 07:17 AM |
Intel On Demand - Validation, certification? | Freddie | 2023/01/30 11:36 AM |
Intel On Demand - Validation, certification? | anon2 | 2023/01/30 07:41 PM |
Intel On Demand - Validation, certification? | anon2 | 2023/01/31 01:35 AM |
Crippleware | Chris G | 2023/01/31 05:47 AM |
Doctorow calls it "enshittification" (NT) | hobold | 2023/01/31 07:55 AM |
Crippleware | anon2 | 2023/01/31 10:51 AM |
Crippleware | Groo | 2023/02/01 02:06 PM |
Crippleware | anon2 | 2023/02/01 05:10 PM |
Crippleware | Chris G | 2023/02/01 05:52 PM |
Crippleware | anon2 | 2023/02/01 09:15 PM |
SPR Volume | me | 2023/02/02 04:47 AM |
SPR Volume | anon2 | 2023/02/02 07:04 AM |
Crippleware | Chris G | 2023/02/02 08:12 AM |
Crippleware | anon2 | 2023/02/02 08:42 AM |
Crippleware | anon2 | 2023/02/02 08:48 AM |
Crippleware | Charles | 2023/02/01 01:38 AM |
Crippleware | Chris G | 2023/02/01 02:59 AM |
language digression | Matt Sayler | 2023/02/01 04:53 PM |
Crippleware | me | 2023/02/01 06:27 PM |
Crippleware | Chris G | 2023/02/01 07:01 PM |
Crippleware | me | 2023/02/01 07:10 PM |
Crippleware | Chris G | 2023/02/01 09:32 PM |
Crippleware | Tony | 2023/02/01 11:18 PM |
Crippleware | me | 2023/02/02 04:27 AM |
Crippleware | anonymou5 | 2023/02/02 03:47 AM |
Crippleware | Chris G | 2023/02/02 05:59 AM |
Intel On Demand - Enshittification | blaine | 2023/01/30 12:13 AM |
Intel and mobile phones | James | 2023/01/29 09:09 AM |
Intel and mobile phones | Maxwell | 2023/01/29 02:25 PM |
Intel and mobile phones | Groo | 2023/01/30 07:20 AM |
Intel and mobile phones | anonymous2 | 2023/01/30 11:15 AM |
Intel and mobile phones | Doug S | 2023/01/30 12:51 PM |
Intel and mobile phones | Daniel B | 2023/01/31 07:37 AM |
Intel and mobile phones | Groo | 2023/02/01 02:03 PM |
SPR HBM | me | 2023/01/29 09:17 AM |
SPR-W | me | 2023/02/17 05:41 PM |
Accelerators on AMD/ARM | Chester | 2023/01/29 05:41 PM |