3 ms·

> You adjust what the query returns to only return the common set. But this shoots the big core in the foot. You run at the lowest common denominator and the b

> You adjust what the query returns to only return the common set. But this shoots the big core in the foot. You run at the lowest common denominator and the big core doesn't have the advantage of higher clocks. And this might just lead to a lot of software that only runs on the big core. Imagine you wanted to fly around between multiple points but if you want the option to ever switch to a bus then your plane will circle around each airport until it's as slow as the bus. Or you can opt for "plane only".

kllrnohj 6y ago
It only shoots the big core in the foot for things that would make meaningful use of the extensions present on the big cores but not on the little ones. Which in a 7w application is what, exactly?
- close04 6y ago
  Anything that uses any AVX or FMA3 off the top of my head. A better mix would have been simply using lower clocked, lower powered cores of the same type or really close derivatives of the big core where the manufacturing process and clocks are what keep power low. Not a mix of Ice Lake and Atom. But right now Intel would throw everything at the wall to see what sticks. And it seems like a good way for developers to make sure their software stays on the big core.
- saagarjha 6y ago
  memcpy?
- Dylan16807 6y ago
  The fact that they put the extensions in implies they expect meaningful use, doesn't it? If not on this specific part, on a future part with multiple big cores.
  - kllrnohj 6y ago
    Meaningful use in a particular market != meaningful use in all markets. AVX2/AVX-512 is great in HPC workloads, for example. But nobody is running an HPC workload on a 7w netbook, now are they? What is useful on Xeon and what is useful on Atom are different. This is an Atom-class SoC used in Atom-class applications, not a Xeon-class one.
    - Dylan16807 6y ago
      That doesn't address what I said at all. This is about extensions that are in this Atom-class SoC.

kllrnohj 6y ago

It only shoots the big core in the foot for things that would make meaningful use of the extensions present on the big cores but not on the little ones. Which in a 7w application is what, exactly?

close04 6y ago
Anything that uses any AVX or FMA3 off the top of my head. A better mix would have been simply using lower clocked, lower powered cores of the same type or really close derivatives of the big core where the manufacturing process and clocks are what keep power low. Not a mix of Ice Lake and Atom. But right now Intel would throw everything at the wall to see what sticks. And it seems like a good way for developers to make sure their software stays on the big core.
saagarjha 6y ago
memcpy?
Dylan16807 6y ago
The fact that they put the extensions in implies they expect meaningful use, doesn't it? If not on this specific part, on a future part with multiple big cores.
- kllrnohj 6y ago
  Meaningful use in a particular market != meaningful use in all markets. AVX2/AVX-512 is great in HPC workloads, for example. But nobody is running an HPC workload on a 7w netbook, now are they? What is useful on Xeon and what is useful on Atom are different. This is an Atom-class SoC used in Atom-class applications, not a Xeon-class one.
  - Dylan16807 6y ago
    That doesn't address what I said at all. This is about extensions that are in this Atom-class SoC.