But there’s a difference between offering a flexible implementation that adjusts clock to ensure the best performance in all scenarios and stuffing a CPU into such a deleterious environment that it has to drop its base clock just to hold performance. There’s nothing intrinsically wrong with CPUs or SoCs that dynamically adjust their clocks in response to operating conditions, and these efficiency improvements have dramatically improved battery life and burst performance in modern systems. Later, Intel introduced the concept of Turbo modes - clock speeds the CPU would boost up to, if thermal conditions and power draw allowed for it. The ability to change the CPU’s clock on the fly was first introduced in mobile CPUs as Intel SpeedStep technology and was used to improve battery life by dropping the CPU clock when the chip was under minimal load. Once upon a time, a CPU’s clock speed was a static number that reflected the operating speed of the CPU at all times (unless you deactivated Turbo Mode to drop back to 4.77MHz - but that’s a story for another day and only relevant to a much earlier class of CPUs).
Based on test reports, the CPU often fails to maintain its base clock under load, dropping to 2.2GHz - well below the 2.9GHz minimum speed promised by Intel and by Apple’s own sales pages.
These issues are not unique to Apple - and we said as much as in our initial coverage - but Apple’s Core i9 implementation appears particularly egregious.
#CPU THROTTLED PRO#
Last week, news broke that Apple’s most recent MacBook Pro refreshes with top-end Intel Core i7 and Core i9 microprocessors have major throttling problems.
0 kommentar(er)
