1 00:00:00,080 --> 00:00:07,839 When you think of memory in your computer, you might think of things like DDR modules, VRAM on your graphics card, 2 00:00:05,920 --> 00:00:13,280 or most likely just hard drives and SSDs. But there's actually another type 3 00:00:10,240 --> 00:00:15,519 of memory that's incredibly fast and 4 00:00:13,280 --> 00:00:21,840 essential to the speed that we've gotten accustomed to with modern computers. I'm 5 00:00:18,480 --> 00:00:23,840 talking about your CPU cache. No, not 6 00:00:21,840 --> 00:00:28,000 the money that you blew on that processor with hyperthreading that you 7 00:00:25,760 --> 00:00:32,239 didn't really need. What we're talking about is cache with an E. It's a 8 00:00:30,560 --> 00:00:36,960 specialized type of memory that's built into your CPU. But why the heck would 9 00:00:35,200 --> 00:00:41,120 your processor need its own memory? Aren't the 16 gigs of RAM or whatever 10 00:00:39,520 --> 00:00:46,239 the heck you already have in your computer good enough? Well, not really, 11 00:00:44,000 --> 00:00:50,640 to be honest. You see, those RAM modules are a heck of a lot faster than say a 12 00:00:49,039 --> 00:00:56,079 hard drive in terms of data transfer. Like a lot faster. But your CPU actually 13 00:00:53,199 --> 00:01:00,480 wants data much faster than your RAM can even provide it. And on top of that, as 14 00:00:58,399 --> 00:01:05,840 CPUs have gotten faster over the years, they continue to outstrip typical RAM 15 00:01:02,960 --> 00:01:10,400 modules by wider and wider margins. Meaning that without faster memory, your 16 00:01:08,159 --> 00:01:15,439 CPU is going to be sitting around doing nothing like a kind of unproductive 17 00:01:12,799 --> 00:01:19,840 employee as it waits for RAM and you'll run into bottlenecks as a result. This 18 00:01:17,680 --> 00:01:25,840 is where cache comes in. Unlike system memory, which consists of dynamic RAM or 19 00:01:22,560 --> 00:01:28,080 DRAM, your CPU cache is static RAM or 20 00:01:25,840 --> 00:01:32,640 SRAMM, which is more expensive and takes up more space, but is much faster than 21 00:01:30,960 --> 00:01:37,360 DRAM because it doesn't have to be constantly refreshed in order to hold 22 00:01:35,040 --> 00:01:41,439 data the way that DRAM has to be. An average CPU will only have a few 23 00:01:39,280 --> 00:01:46,399 megabytes of cache, but it makes a tremendous use of this small amount of 24 00:01:43,920 --> 00:01:51,040 memory. You see, when a CPU accesses something from your main system RAM, it 25 00:01:48,720 --> 00:01:56,399 generally stores it in its cache, then uses complex algorithms to guess as to 26 00:01:54,240 --> 00:02:00,799 what other instructions or data it might need next. And it fetches those from 27 00:01:58,719 --> 00:02:05,920 your system RAM as well. Since these guesses aren't perfect, CPUs suffer from 28 00:02:03,520 --> 00:02:10,399 things called cache misses, where it searches its own cache, can't find what 29 00:02:08,160 --> 00:02:15,040 it needs, and has to access your system memory directly instead, which slows 30 00:02:13,040 --> 00:02:19,280 things down. Fortunately, however, modern processors have gotten pretty 31 00:02:16,879 --> 00:02:24,560 good at deciding what to put inside their caches, as they'll typically have 32 00:02:21,520 --> 00:02:26,800 a cache hit rate of better than 80%. 33 00:02:24,560 --> 00:02:31,760 Meaning that most of the time, your CPU is only processing what it finds in 34 00:02:29,360 --> 00:02:36,480 cache and doesn't have to bother talking to your slower system memory at all. And 35 00:02:34,239 --> 00:02:40,800 as you may have guessed, more cache is advantageous. So, when you're shopping 36 00:02:38,480 --> 00:02:46,800 for a processor, the product page will indicate how much level three or L3 37 00:02:43,680 --> 00:02:49,200 cache is built in with higherend modules 38 00:02:46,800 --> 00:02:53,760 having a few extra megabytes. And if you're wondering what the heck happened 39 00:02:50,879 --> 00:02:58,879 to levels one and two, these are smaller, even faster parts of the cache 40 00:02:56,160 --> 00:03:02,959 that your CPU will try and hit before looking for data in your level three 41 00:03:00,879 --> 00:03:09,040 cache. Okay, Luke, that's cool and all, but will better cache actually give me 42 00:03:05,040 --> 00:03:11,599 more FPS in games or faster speeds in my 43 00:03:09,040 --> 00:03:15,360 other stuff? Well, this can depend on the specific application, but you can 44 00:03:13,599 --> 00:03:20,319 see performance increases kind of overall on CPUs with larger caches. 45 00:03:18,480 --> 00:03:25,360 Fortunately, though, if you're buying a higherend processor because you need 46 00:03:22,560 --> 00:03:30,000 more cores, higher IPCs, or better overclocking potential in general, it'll 47 00:03:27,920 --> 00:03:34,640 probably come with more cash as well. So, it's not really something that you 48 00:03:31,360 --> 00:03:36,720 have to really think about too much. Of 49 00:03:34,640 --> 00:03:41,599 course, if you really want that high-end silicon, make sure that you're paying 50 00:03:38,640 --> 00:03:45,360 attention to how much cash with an S that your wallet has left. Are you 51 00:03:43,680 --> 00:03:48,879 trying to program payments into your app and it's just not that easy? If you're 52 00:03:47,200 --> 00:03:53,920 building a mobile app and searching for a simple payment solution, check out 53 00:03:50,879 --> 00:03:56,400 Brainree. Brainree's V.0 SDK is one 54 00:03:53,920 --> 00:03:59,680 amazingly simple integration away from giving you simple payments every time. 55 00:03:58,560 --> 00:04:04,560 Developers around the world have embraced the Brainree V.0 SDK as the 56 00:04:02,480 --> 00:04:08,080 easiest way to add secure mobile payments to their apps and websites. 57 00:04:06,000 --> 00:04:12,319 Once integrated, Brainree supports a bunch of different ways to pay like 58 00:04:09,439 --> 00:04:16,160 Apple Pay, Android Pay, PayPal, Venmo, credit cards, and even Bitcoin. And if 59 00:04:14,560 --> 00:04:20,560 something new pops up, Brainree will support that, too. It's used by Uber, 60 00:04:18,079 --> 00:04:24,400 Airbnb, GitHub. It's scalable. It integrates into your app easily. Just a 61 00:04:22,639 --> 00:04:28,240 few lines of code. Try it in the sandbox. Learn more about Brainree in 62 00:04:26,560 --> 00:04:34,199 the video description down below. and get your first 50,000 in transactions 63 00:04:31,120 --> 00:04:35,360 fee free at 64 00:04:34,199 --> 00:04:38,800 brainttreeepayments.com/techquicky. But are you cashed out? If you are, be sure 65 00:04:37,360 --> 00:04:42,479 to like the video, dislike the video, subscribe, do all those fun things. And 66 00:04:40,400 --> 00:04:46,639 on your way out the door, be sure to check out channel Superfund right across 67 00:04:44,160 --> 00:04:51,199 the street. They're fantastic. Highly recommended. And as always, leave a 68 00:04:49,199 --> 00:04:54,320 comment on the little book as you as you leave with the suggestions that you 69 00:04:52,800 --> 00:04:59,040 might have for how we could make your stay even more better next time. And 70 00:04:57,280 --> 00:05:02,960 anyways, thank you for enjoying Techquiki. We'll see you again.