goldstone77 :
Just because someone shares your views that does not in itself eliminate bias. Multiple sources(you name 4) that you have previously used as points of reference share unfavorable reviews of Intel, so you now call them bias. That is the definition of bias. I'm done talking on the subject.
My comment demonstrated that I am not alone, despite all your continuous pretension that I am the only can see the bias on the reviews that you bring to us. And of course you omit entirely that I am not only reporting the biased reviews, but I also explain the dirty tricks used to favor AMD hardware. A short list of the dirty tricks used directly by AMD in demos and marketing slides or by the biased review that favors AMD:
- Testing games at higher resolutions such as 4K, generating a GPU bottleneck and reducing the performance gap between Intel and AMD CPUs.
- Measure power consumption on a workload that supports 512bit to get the SIMD units on Skylake-X fully loaded, then measure performance on a workload with 128bit support for not giving Intel any performance advantage (SIMD units in Intel CPUs only one half or one fourth loaded). Evidently this dirty trick will favor performance/power ratio for AMD.
- Disable Turbo on Intel chips to reduce performance.
- Disable quad-channel on Intel boards to reduce performance.
- Run EPYC vs Broadwel Xeon workload with the memory crippled on the Xeon chip, and run a memory bound workload to maximize the effect of crippling.
- Run SPEC benchmarks for EPYC and Broadwell Skylake Xeons and magically the performance of Xeon is 40% slower than usual and Skylake Xeon is 60% slower than real.
- If AMD Zen shines on rendering then add three or four rendering applications to the testing suite, and also test the same application (e.g. Blender) twice to give more wins to AMD and move the average performance towards them.
- Use a motherboard explicitly incompatible with the SKL-X model used, ignoring AsRock warning, and when the CPU is damaged, make a photo of the burn and spread it on twitter, pretending that the CPU was defective or something.
- Use an engineering sample for Intel instead a retail CPU, and don't say it in the review.
- Use GPU-bound and frame-limit settings to reduce the performance gap between AMD and Intel. Then overclocks both chips to reduce the gap still more (Intel CPUs are bottlenecked), when someone mentions the obvious problem in the numbers given, the reviewer answers in tweeter that he doesn't know what is happening and invent a fake excuse to why Intel chips are slower than expected.
- Compare overclocked AMD vs stock Intel, but label both chips as stock in the graphs and in the text.
- Use the latest BIOS/AGESA for AMD, and repeat the review when new AGESA versions are available. Use beta BIOS for SKL-X, and don't repeat the review even when final BIOS with turbo 3.0 correctly working and p-states is available.
- Write a rant article when der8hauer has something bad to say about Intel. Remains silent when he has something good to say.
- And so on.