text stringlengths 14 502 |
|---|
[2587.20 --> 2588.38] So it wasn't really relevant, |
[2588.46 --> 2589.24] and they sucked more power. |
[2589.50 --> 2590.24] They didn't overclock. |
[2590.36 --> 2591.30] There was a bunch of things. |
[2592.32 --> 2593.84] So, people were excited |
[2593.84 --> 2597.46] because Zen would bring more competition to the market. |
[2597.46 --> 2600.78] Now, getting back to AMD's previous cores, |
[2601.06 --> 2604.22] not necessarily being that underpowered for gaming, |
[2604.32 --> 2606.76] well, that's what you're seeing on the game consoles. |
[2607.50 --> 2608.84] So because the game developers |
[2608.84 --> 2611.48] know exactly what hardware they're optimizing for, |
[2611.48 --> 2612.22] they can go, |
[2612.22 --> 2614.92] okay, we're going to have exactly this. |
[2615.02 --> 2615.34] Oh, right. |
[2615.38 --> 2617.90] The other issue with Zen performance on the desktop and games |
[2617.90 --> 2620.56] was actually more software and firmware related. |
[2620.70 --> 2622.48] There were scheduler issues with Windows, |
[2623.02 --> 2625.60] and there were, I mean, any new CPU. |
[2625.86 --> 2627.32] It's kind of like why I put, |
[2629.62 --> 2630.82] what was the, |
[2630.82 --> 2633.68] what was the not set of the 6950Xs |
[2633.68 --> 2635.12] in the editing machines, |
[2635.30 --> 2636.50] like three weeks before |
[2636.50 --> 2638.52] the new 18 core flagship came out. |
[2638.52 --> 2639.82] The reason is that |
[2639.82 --> 2641.36] anytime you have a new CPU launch, |
[2641.42 --> 2642.52] whether it's AMD or Intel, |
[2642.62 --> 2644.32] and particularly on this last round, |
[2644.60 --> 2646.34] where both AMD and Intel |
[2646.34 --> 2648.30] were guilty of pulling up their launches |
[2648.30 --> 2649.94] just to like, |
[2650.00 --> 2651.34] just to have something out there |
[2651.34 --> 2653.90] and them being not quite 100% polished, |
[2654.54 --> 2656.28] anytime you have a new CPU, |
[2656.44 --> 2657.96] you're going to have some issues. |
[2658.66 --> 2661.38] And that was a big part |
[2661.38 --> 2663.12] of what affected gaming performance on the desktop. |
[2663.26 --> 2664.48] And sometimes game developers |
[2664.48 --> 2665.54] did have to optimize |
[2665.54 --> 2667.14] because even though it's x86, |
[2668.20 --> 2670.82] it's not like a new CPU |
[2670.82 --> 2672.82] is just the old CPU, |
[2672.98 --> 2674.90] but like with a Trogdor, |
[2675.32 --> 2676.08] like arm, |
[2676.32 --> 2680.22] like it's actually different. |
[2681.60 --> 2683.04] And so if you gave, |
[2683.24 --> 2683.88] even if let's say |
[2683.88 --> 2685.40] you gave a professional driver, |
[2686.20 --> 2688.84] and I don't know cars, |
[2689.14 --> 2690.18] but so you'll have to forgive me, |
[2690.22 --> 2691.42] but let's say you gave them |
[2691.42 --> 2693.94] a Bugatti and a Lamborghini, |
[2694.50 --> 2695.62] some model, |
[2695.72 --> 2696.44] X and Y, |
[2696.64 --> 2697.28] and you were like, |
[2697.36 --> 2697.58] okay, |
[2697.74 --> 2698.92] get the best track time |
[2698.92 --> 2700.36] on this track. |
[2701.40 --> 2702.98] It would take them a little while |
[2702.98 --> 2704.16] if they switched from this one |
[2704.16 --> 2704.72] to that one |
[2704.72 --> 2706.12] to learn the best way to do it, |
[2706.14 --> 2707.40] even if this one was more powerful. |
[2708.08 --> 2708.86] Like they are, |
[2708.98 --> 2710.46] they're different machines. |
[2711.58 --> 2713.54] So coming back to consoles, |
[2713.64 --> 2714.64] this has been a very sort of |
[2714.64 --> 2715.70] winding topic here. |
[2716.64 --> 2717.46] They know exactly |
[2717.46 --> 2718.50] what they're optimizing for. |
[2718.50 --> 2720.04] They don't have to make any guesses |
[2720.04 --> 2722.42] and they are going to |
[2722.42 --> 2724.58] run the game in such a way |
[2724.58 --> 2725.34] and they're going to optimize |
[2725.34 --> 2726.18] the game in such a way |
[2726.18 --> 2727.02] that you aren't going to run |
[2727.02 --> 2727.96] out of CPU resources. |
[2728.48 --> 2730.02] Also, by the end of AMD's |
[2730.02 --> 2730.84] non-Zen cores, |
[2730.98 --> 2732.34] while the performance wasn't great, |
[2732.46 --> 2733.36] their power efficiency |
[2733.36 --> 2735.00] was getting a lot better. |
[2735.82 --> 2737.02] So they take this good |
[2737.02 --> 2737.62] power efficiency |
[2737.62 --> 2738.42] and they've got four |
[2738.42 --> 2740.36] kind of like good enough cores |
[2740.36 --> 2741.84] and they've got developers |
[2741.84 --> 2743.56] who know that they can split it up |
[2743.56 --> 2744.76] exactly in this way |
[2744.76 --> 2745.44] because it's going to run |
[2745.44 --> 2746.60] on four cores. |
[2746.72 --> 2747.24] There's not going to be |
[2747.24 --> 2748.26] some Yahoo out there |
[2748.26 --> 2749.10] running a dual core |
[2749.10 --> 2751.40] because Intel still has |
[2751.40 --> 2753.56] dual cores for some reason |
[2753.56 --> 2756.60] and they can split it up |
[2756.60 --> 2757.20] that way to make |
[2757.20 --> 2758.24] the best possible use |
[2758.24 --> 2759.06] of the quad core. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.