4 ms·

I have not watched Intel closely for a long time. Seeing that its market cap is down 30% over the last decade is crazy. Considering how IT in general grew so mu

I have not watched Intel closely for a long time. Seeing that its market cap is down 30% over the last decade is crazy. Considering how IT in general grew so much over the same time period. What happened? To see how the Intel CEO is thinking, I now scrolled through a few interviews with him. In this interview, Intel's CEO is asked to describe the difference of a CPU and a GPU: https://www.youtube.com/watch?v=d07wy5AK72E https://www.youtube.com/watch?v=d07wy5AK72E His answer is that the CPU is capable of doing general computing, while a GPU is made for very specific tasks. I'm not sure if that is a good way to put it. The way I would put it is that a GPU is a bit like an array of many CPUs. And to manage this array of processors all doing computation at the same time brings constraints and management overhead. So it is usually harder to program a GPU but results in better performance.

hmottestad 2y ago
The article sheds some light on what’s been going on. You’ll also be happy to know that the video you linked to is not a video of the current Intel CEO.
- ArtTimeInvestor 2y ago
  But he's the CEO under whom things went downhill, right?
  - hmottestad 2y ago
    I wouldn't say so no. Personally I feel that the 5 years of reintroducing 14nm instead of getting 10nm out the door was what ate up any lead that Intel had over its competitors. And don't forget that rumors has it that Apple reported more bugs with Intel Skylake than the QA team at Intel had managed to report. Never a good thing when one of your biggest customers finds more bugs in your product than your own engineers have managed to find. I wouldn't really blame all this on a single person though.
Nevermark 2y ago
I think you are right about CPU vs. GPU. It’s complex independent cores vs. simple array cores. The largest part of that “overhead” is the need for much higher memory bandwidth and caching due to having many more cores to feed. And the added complexity of programming is managing groups of cores (and multiple groups of cores) so they are all as active as possible without blocking each other algorithmically or due to memory misalignments, page read/write inconsistency, or cross interference. With many more cores achieved with smaller cores: streamlined Arithmetic Control Units, less pipelining (?) and a simpler/shared Instruction Control Unit. Somebody correct me if I am wrong.
- JonChesterfield 2y ago
  The CPU for complex stuff and GPU for simple number crushing is a really popular narrative. It's true in one sense and nonsense in another, determined solely on the software it's running. If your program has one or two threads and spends all its time doing branchy control flow, a CPU will run it adequately and a GPU very poorly. If the program has millions of mostly independent tasks, a GPU will run it adequately and a CPU very poorly. That's the two limiting cases though and quite a lot of software sits somewhere in the middle. The most concise distinction to draw between the hardware architectures is what they do about memory latency. We want lots of memory, that means it ends up far from the cores, so you have to do something while you wait for accesses to it. Fast CPUs use branch predictors and deep pipelines to keep the cores busy, fast GPUs keep a queue of coroutines ready to go and pick a different one to step along when waiting for memory. That's roughly why CPUs have a few threads - all the predictor and wind back logic is expensive. It's also why GPUs have many - no predictor or wind back logic, but you need to have a lot of coroutines ready to go to keep the latency hidden. Beyond that, there's nothing either CPU or GPU can do that the other cannot. They're both finite approximations to Turing machines. There are some apparent distinctions from the hosted OS abstraction where the CPU threads get "syscall" and the GPU threads need to DIY their equivalent but the application doesn't care. Threads on either can call fprintf just fine. It makes a bit of a mess in libc but that's alright (and done in LLVM already).
  - Nevermark 2y ago
deelowe 2y ago
In a nutshell, Intel's board was focused on extracting value from the company instead of innovating. While this was going on, compute was undergoing a transformation as everything transitioned to cloud solutions. By the time they realized, it was too late and the rot had set in. Now the company is full of mediocre middle managers and principles who spend all day playing politics instead of working on real problems.
- ArtTimeInvestor 2y ago
  board was focused on extracting value from the company From the company? Extract to where?
  - orwin 2y ago
    Their own pocket I'd wager. A simple way to check if a board/CEO wants to extract a lot of future value _now_ is to look into their accounting, and especially how they count physical assets. If they count physical assets at their current selling price, you can probably get in long-term. If they count them at their buying prices you might have to worry. If they do 'future accounting', tying into assets their estimated future added value, you can be sure the current owners are extracting the most they can _now_ and will try to drop the bag into futures investors (or ask for a government bailout)
    - ArtTimeInvestor 2y ago
      What is the selling price of physical assets? I would think Intel is not a reseller, so they don't buy and sell stuff but rather buy raw materials and then transform them into a CPU? And how would counting physical assets at their buying price move money from the company into the pocket of the CEO?
      - orwin 2y ago
        Let's say Company A buy a machine to engrave CPU 10 millions (no idea of the real cost), half of it with debt. In normal/traditional accounting, you put the selling price of the machine (if you have to liquidate the company) on the side of the asset: let's say 8 millions the first year, and 5 million on the debt side (they bought it with 5 million of investment money, leveraged with debt). Company has 8 millions in assets, 5 million in debt: good ratio, healthy company. Company B use future accounting: it buy the 10 million dollars machine. On the 'asset' side, you put 16 millions: the machine is worth 8, and is expected to earn the company a net profit of 8 during its lifetime. On the 'debt' side, you put 5. 16/5, the ratio is truly excellent. So good even that you can afford to take another 5 millions, and buy share/issue dividends. Now your asset/debt ratio is 16/10=8/5, same as Company A, except either your current shareholders have already reimbursed the initial investment, derisking themselves totally if the company ends up failing. I think you have a Republican primary candidate who used that with his drug company, the company failed to produce anything of value, but only late investors lost anything.
ksec 2y ago
>I'm not sure if that is a good way to put it. His explantation is actually closer to the truth than your array of many CPUs. Because GPU isn't that. It is / was moving in that direction but it is certain not many CPU or Intel Larrabee.

hmottestad 2y ago

The article sheds some light on what’s been going on. You’ll also be happy to know that the video you linked to is not a video of the current Intel CEO.

ArtTimeInvestor 2y ago
But he's the CEO under whom things went downhill, right?
- hmottestad 2y ago
  I wouldn't say so no. Personally I feel that the 5 years of reintroducing 14nm instead of getting 10nm out the door was what ate up any lead that Intel had over its competitors. And don't forget that rumors has it that Apple reported more bugs with Intel Skylake than the QA team at Intel had managed to report. Never a good thing when one of your biggest customers finds more bugs in your product than your own engineers have managed to find. I wouldn't really blame all this on a single person though.

Nevermark 2y ago

I think you are right about CPU vs. GPU. It’s complex independent cores vs. simple array cores. The largest part of that “overhead” is the need for much higher memory bandwidth and caching due to having many more cores to feed. And the added complexity of programming is managing groups of cores (and multiple groups of cores) so they are all as active as possible without blocking each other algorithmically or due to memory misalignments, page read/write inconsistency, or cross interference. With many more cores achieved with smaller cores: streamlined Arithmetic Control Units, less pipelining (?) and a simpler/shared Instruction Control Unit. Somebody correct me if I am wrong.

JonChesterfield 2y ago
The CPU for complex stuff and GPU for simple number crushing is a really popular narrative. It's true in one sense and nonsense in another, determined solely on the software it's running. If your program has one or two threads and spends all its time doing branchy control flow, a CPU will run it adequately and a GPU very poorly. If the program has millions of mostly independent tasks, a GPU will run it adequately and a CPU very poorly. That's the two limiting cases though and quite a lot of software sits somewhere in the middle. The most concise distinction to draw between the hardware architectures is what they do about memory latency. We want lots of memory, that means it ends up far from the cores, so you have to do something while you wait for accesses to it. Fast CPUs use branch predictors and deep pipelines to keep the cores busy, fast GPUs keep a queue of coroutines ready to go and pick a different one to step along when waiting for memory. That's roughly why CPUs have a few threads - all the predictor and wind back logic is expensive. It's also why GPUs have many - no predictor or wind back logic, but you need to have a lot of coroutines ready to go to keep the latency hidden. Beyond that, there's nothing either CPU or GPU can do that the other cannot. They're both finite approximations to Turing machines. There are some apparent distinctions from the hosted OS abstraction where the CPU threads get "syscall" and the GPU threads need to DIY their equivalent but the application doesn't care. Threads on either can call fprintf just fine. It makes a bit of a mess in libc but that's alright (and done in LLVM already).
- Nevermark 2y ago

deelowe 2y ago

In a nutshell, Intel's board was focused on extracting value from the company instead of innovating. While this was going on, compute was undergoing a transformation as everything transitioned to cloud solutions. By the time they realized, it was too late and the rot had set in. Now the company is full of mediocre middle managers and principles who spend all day playing politics instead of working on real problems.

ArtTimeInvestor 2y ago
board was focused on extracting value from the company From the company? Extract to where?
- orwin 2y ago
  Their own pocket I'd wager. A simple way to check if a board/CEO wants to extract a lot of future value _now_ is to look into their accounting, and especially how they count physical assets. If they count physical assets at their current selling price, you can probably get in long-term. If they count them at their buying prices you might have to worry. If they do 'future accounting', tying into assets their estimated future added value, you can be sure the current owners are extracting the most they can _now_ and will try to drop the bag into futures investors (or ask for a government bailout)
  - ArtTimeInvestor 2y ago
    What is the selling price of physical assets? I would think Intel is not a reseller, so they don't buy and sell stuff but rather buy raw materials and then transform them into a CPU? And how would counting physical assets at their buying price move money from the company into the pocket of the CEO?
    - orwin 2y ago
      Let's say Company A buy a machine to engrave CPU 10 millions (no idea of the real cost), half of it with debt. In normal/traditional accounting, you put the selling price of the machine (if you have to liquidate the company) on the side of the asset: let's say 8 millions the first year, and 5 million on the debt side (they bought it with 5 million of investment money, leveraged with debt). Company has 8 millions in assets, 5 million in debt: good ratio, healthy company. Company B use future accounting: it buy the 10 million dollars machine. On the 'asset' side, you put 16 millions: the machine is worth 8, and is expected to earn the company a net profit of 8 during its lifetime. On the 'debt' side, you put 5. 16/5, the ratio is truly excellent. So good even that you can afford to take another 5 millions, and buy share/issue dividends. Now your asset/debt ratio is 16/10=8/5, same as Company A, except either your current shareholders have already reimbursed the initial investment, derisking themselves totally if the company ends up failing. I think you have a Republican primary candidate who used that with his drug company, the company failed to produce anything of value, but only late investors lost anything.

ksec 2y ago

>I'm not sure if that is a good way to put it. His explantation is actually closer to the truth than your array of many CPUs. Because GPU isn't that. It is / was moving in that direction but it is certain not many CPU or Intel Larrabee.