One more thing I want to say is another reason Intel is so far ahead of AMD is because of bad business practices by Intel. They repeatedly do illegal maneuvers against AMD to screw over AMD.
LIKE THIS STUFF
"The biggest case is in Europe, where regulators have fined Intel a record $1.45 billion over what they described as Intel's illegal tactics to bully PC makers into choosing Intel chips over AMD's. EU spokesman Jonathan Todd said that the European Commission "takes note" of Intel's settlement with AMD but that it does not change Intel's duty to comply with European antitrust law.
Intel is also fighting an $18.6 million fine in Korea and a federal lawsuit filed last week by New York Attorney General Andrew Cuomo, who accused Intel of abusing its dominance to "rule with an iron fist." The U.S. Federal Trade Commission also is investigating"
AND LIKE THIS STUFF.
"Here's something you probably don't know, but really should - especially if you're a programmer, and especially especially if you're using Intel's compiler. It's a fact that's not widely known, but Intel's compiler deliberately and knowingly cripples performance for non-Intel (AMD/VIA) processors.
Agner Fog details this particularly nasty examples of Intel's anticompetitive practices quite well. Intel's compiler can produce different versions of pieces of code, with each version being optimised for a specific processor and/or instruction set (SSE2, SSE3, etc.). The system detects which CPU it's running on and chooses the optimal code path accordingly; the CPU dispatcher, as it's called.
"However, the Intel CPU dispatcher does not only check which instruction set is supported by the CPU, it also checks the vendor ID string," Fog details, "If the vendor string says 'GenuineIntel' then it uses the optimal code path. If the CPU is not from Intel then, in most cases, it will run the slowest possible version of the code, even if the CPU is fully compatible with a better version."
It turns out that while this is known behaviour, few users of the Intel compiler actually seem to know about it. Intel does not advertise the compiler as being Intel-specific, so the company has no excuse for deliberately crippling performance on non-Intel machines."
They have been crippling AMD CPUS for years and years. AND there is also a lot of other illegal stuff Intel does to screw over their competitors.
LIKE THIS STUFF
"The biggest case is in Europe, where regulators have fined Intel a record $1.45 billion over what they described as Intel's illegal tactics to bully PC makers into choosing Intel chips over AMD's. EU spokesman Jonathan Todd said that the European Commission "takes note" of Intel's settlement with AMD but that it does not change Intel's duty to comply with European antitrust law.
Intel is also fighting an $18.6 million fine in Korea and a federal lawsuit filed last week by New York Attorney General Andrew Cuomo, who accused Intel of abusing its dominance to "rule with an iron fist." The U.S. Federal Trade Commission also is investigating"
AND LIKE THIS STUFF.
"Here's something you probably don't know, but really should - especially if you're a programmer, and especially especially if you're using Intel's compiler. It's a fact that's not widely known, but Intel's compiler deliberately and knowingly cripples performance for non-Intel (AMD/VIA) processors.
Agner Fog details this particularly nasty examples of Intel's anticompetitive practices quite well. Intel's compiler can produce different versions of pieces of code, with each version being optimised for a specific processor and/or instruction set (SSE2, SSE3, etc.). The system detects which CPU it's running on and chooses the optimal code path accordingly; the CPU dispatcher, as it's called.
"However, the Intel CPU dispatcher does not only check which instruction set is supported by the CPU, it also checks the vendor ID string," Fog details, "If the vendor string says 'GenuineIntel' then it uses the optimal code path. If the CPU is not from Intel then, in most cases, it will run the slowest possible version of the code, even if the CPU is fully compatible with a better version."
It turns out that while this is known behaviour, few users of the Intel compiler actually seem to know about it. Intel does not advertise the compiler as being Intel-specific, so the company has no excuse for deliberately crippling performance on non-Intel machines."
They have been crippling AMD CPUS for years and years. AND there is also a lot of other illegal stuff Intel does to screw over their competitors.