WEBVTT

00:00:00.030 --> 00:00:05.910
have you ever noticed that when you want to find out what speed your CPU or

00:00:04.140 --> 00:00:10.440
graphics card runs that there's a bunch of seemingly conflicting information

00:00:08.069 --> 00:00:14.309
well the way processors work has changed in amazing ways over the last couple of

00:00:12.660 --> 00:00:17.640
decades but one of the most remarkable things about modern microprocessors

00:00:15.870 --> 00:00:21.960
whether we're talking about the ones that go in your phone your PC or even in

00:00:19.470 --> 00:00:25.769
a massive server is their ability to dynamically deliver only the performance

00:00:24.060 --> 00:00:29.910
that's needed at a given moment I'll explain why they do this but first a bit

00:00:27.630 --> 00:00:35.579
of history it didn't always work this way when I was growing up a 486 TX 33

00:00:33.120 --> 00:00:39.180
megahertz processor ran it 33 megahertz gosh darn it and if 33 megahertz was

00:00:37.770 --> 00:00:44.789
good enough for when it was working hard then it was good enough rone it was sitting around doing nothing - and that

00:00:42.870 --> 00:00:50.190
was fine well a couple of things were still true first is that processors ran

00:00:47.219 --> 00:00:54.780
so cool that they just needed tiny small thin heat sinks on the MOR at worst a

00:00:52.110 --> 00:01:00.210
very small fan and second is that the laptop mobile PC revolution hadn't

00:00:57.840 --> 00:01:03.719
started yet and a little extra power consumption is a relatively small deal

00:01:02.219 --> 00:01:09.689
if you're not trying to power something off of a battery well that changed fast

00:01:06.780 --> 00:01:14.010
Intel and AMD were locked in an arms race to see who could create that

00:01:11.189 --> 00:01:17.700
fastest desktop CPUs voltages and power were pumped up and existing design

00:01:16.439 --> 00:01:21.840
architectures were pushed to their limits all without worrying too much

00:01:19.770 --> 00:01:26.189
about efficiency in pursuit of the almighty gigahertz barrier and beyond to

00:01:24.479 --> 00:01:30.540
hell with cool and quiet I mean to put this in perspective from 1996 to 2000

00:01:28.860 --> 00:01:36.150
alone stop cooling went from looking like this to looking like this but that

00:01:33.780 --> 00:01:40.979
all came at a cost your power bill aside more power consumption produces waste

00:01:38.520 --> 00:01:46.560
heat and when a processor runs hot all the time its lifespan is reduced

00:01:43.100 --> 00:01:48.600
something had to be done but what if you

00:01:46.560 --> 00:01:52.380
could run at benchmark crushing high performance frequencies when needed and

00:01:50.490 --> 00:01:57.869
turned down the juice the rest of the time well that's exactly what happened

00:01:55.110 --> 00:02:02.430
Intel speedstep was born all right light it so that's a lot of preamble but why

00:01:59.880 --> 00:02:07.619
does my CPU or graphics card have these ambiguous specifications well because

00:02:05.460 --> 00:02:10.860
while all this was happening a mobile revolution was occurring and when you're

00:02:09.629 --> 00:02:15.870
going to be running off of a battery power consumption sits in the fur seat

00:02:13.409 --> 00:02:20.580
and raw performance sits in the back so the philosophies of the processor makers

00:02:17.970 --> 00:02:24.930
changed and we stopped getting massive leaps in single core performance but

00:02:23.040 --> 00:02:29.370
computing demands also didn't stand still so they needed a different

00:02:26.549 --> 00:02:34.860
solution back to this graph a lower clock processor core actually consumes

00:02:31.739 --> 00:02:37.019
so much less power that you can put more

00:02:34.860 --> 00:02:41.220
than one of them on a CPU instead of a single high-performance core for better

00:02:39.390 --> 00:02:46.890
overall performance and optimized workloads multi-core processors were

00:02:43.860 --> 00:02:48.540
born but some applications don't benefit

00:02:46.890 --> 00:02:52.410
from these additional cores and we still need to crush single threaded

00:02:49.920 --> 00:02:58.590
performance from time to time and that's what a CPU with Intel turbo booth does

00:02:55.160 --> 00:03:01.319
unlike speed steps outright performance

00:02:58.590 --> 00:03:05.879
reduction it actually redirects power from coarse that aren't needed and

00:03:03.709 --> 00:03:10.560
sacrifices some efficiency in the remaining core or course to boost up the

00:03:08.670 --> 00:03:15.870
clock speeds to a predetermined limit and that is what we see when we look at

00:03:13.140 --> 00:03:21.209
CPU specifications a nominal frequency that all course can reach at the same

00:03:18.120 --> 00:03:23.669
time and an amped-up boosted frequency

00:03:21.209 --> 00:03:28.470
that a single core can reach as long as thermal and power limits allow it when

00:03:26.190 --> 00:03:33.510
you need the extra juice this type of dynamic power on-demand design isn't

00:03:31.079 --> 00:03:37.230
unique to Intel either NVIDIA GPU boost boosts the entire processor rather than

00:03:35.760 --> 00:03:41.669
redirecting power from one part to another but similarly looks for

00:03:39.480 --> 00:03:46.200
sufficiently low power consumption and temperatures and increases performance

00:03:43.440 --> 00:03:50.519
on demand pretty cool stuff hey speaking of pretty cool my CPU when it's idle

00:03:48.540 --> 00:03:55.139
yeah sorry no awkward segue today since our sales team didn't manage to sell an

00:03:52.919 --> 00:03:58.620
add integration on this video so that's all that's left is for me to thank you

00:03:56.639 --> 00:04:02.010
guys for watching pathetically beg you to like and share the video or dislike

00:04:00.480 --> 00:04:07.310
it if you hate it I think that's fine too and remind you to subscribe if you

00:04:03.989 --> 00:04:07.310
haven't already see you next time
