Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

See the CPU execution, Pipeline stages and Caches in action. This emulator animates the high level CPU and Cache state-machine. You can track the state (fetch, decode, execute, memory access, write back and ) of a given instruction... Try it here:

Piyush Itankar

10,087 subscribers

110,474 views • 1 year ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

4 Comments

Matt Figdore2 years ago

This is the biggest productivity cheat code right now. Kiss reading documents goodbye. You can get an instant summary of any document with this tool.

William Selby1 year ago

So cool!

Forestman1 year ago

Impressive, very nice. Great learning tool

Oron Port1 year ago

@splinedrive you might be interested

Related Videos

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.

Piyush Itankar

28,019 views • 1 year ago

i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS

i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS

Rebane

1,074,666 views • 4 months ago

Every year I use ZERO "Run plays" for the CPU in #NBA2K26 and a lot of people ask why. People think it causes the CPU to never run plays, but as you can see if you can balance the individual player tendencies correctly the result is a smooth authentic CPU offensive experience.

Every year I use ZERO "Run plays" for the CPU in #NBA2K26 and a lot of people ask why. People think it causes the CPU to never run plays, but as you can see if you can balance the individual player tendencies correctly the result is a smooth authentic CPU offensive experience.

Shady 🧊

184,692 views • 4 months ago

A year ago I made a video about the RIDL CPU vulnerability. In case you haven't seen it, here it is uploaded to Twitter directly! The most interesting part of this has been learning about the prior research that later lead to the discovery of these modern side-channel vulnerabilities. I also spend more time explaining "speculative execution" and how these CPU cache timings can be used as a side-channel. If you haven't seen it yet, give it another chance :)

A year ago I made a video about the RIDL CPU vulnerability. In case you haven't seen it, here it is uploaded to Twitter directly! The most interesting part of this has been learning about the prior research that later lead to the discovery of these modern side-channel vulnerabilities. I also spend more time explaining "speculative execution" and how these CPU cache timings can be used as a side-channel. If you haven't seen it yet, give it another chance :)

LiveOverflow 🔴

18,144 views • 2 years ago

The computer in Minecraft, got bigger! Ryan Boulds recreated real a CPU using redstone logic gates, adders, registers, memory. The build includes over a million blocks and can run arithmetic, comparisons, and even custom programs. He designed machine language to control it.

The computer in Minecraft, got bigger! Ryan Boulds recreated real a CPU using redstone logic gates, adders, registers, memory. The build includes over a million blocks and can run arithmetic, comparisons, and even custom programs. He designed machine language to control it.

Brian Roemmele

295,417 views • 7 months ago

If you have an Intel CPU with AMD GPU and play at 1080p or are massively CPU bound in game... I HIGHLY recommend trying re size bar off in options.4 file and smart access memory "off" in the AMD adrenaline software "tuning" tab.

If you have an Intel CPU with AMD GPU and play at 1080p or are massively CPU bound in game... I HIGHLY recommend trying re size bar off in options.4 file and smart access memory "off" in the AMD adrenaline software "tuning" tab.

MurkTweaks

114,153 views • 2 years ago

Fading out audio is one of the most CPU-intensive tasks you can possibly do! When numbers get really small, the number of CPU operations can explode 100-fold. In this LaurieWired video, we'll explore the IEEE 754 standard, the fight between Intel and DEC, and more!

Fading out audio is one of the most CPU-intensive tasks you can possibly do! When numbers get really small, the number of CPU operations can explode 100-fold. In this LaurieWired video, we'll explore the IEEE 754 standard, the fight between Intel and DEC, and more!

LaurieWired

403,177 views • 11 months ago

CPU Cores, Cachelines, and False Sharing Have you ever heard of "False Sharing"? A performance issue arising when independent variables end up in the same cache line and are being updated by respective threads in parallel. Each CPU core update causes a forceful flushing of the cache line for other cores - even though the variables aren't shared! Check the kernel documentation on this topic, too. There is an excellent video showing this in more detail and a fantastic blog article from Netflix Engineering showing how this impacted production - an excellent case study.

CPU Cores, Cachelines, and False Sharing Have you ever heard of "False Sharing"? A performance issue arising when independent variables end up in the same cache line and are being updated by respective threads in parallel. Each CPU core update causes a forceful flushing of the cache line for other cores - even though the variables aren't shared! Check the kernel documentation on this topic, too. There is an excellent video showing this in more detail and a fantastic blog article from Netflix Engineering showing how this impacted production - an excellent case study.

Vivek Galatage

60,470 views • 1 year ago

So a #Madden26 modder named snowmonkey changed the CPU vs CPU camera to be from the head coaches point of view and I love it lol. If you turn off the commentary its like you're in the stadium!

So a #Madden26 modder named snowmonkey changed the CPU vs CPU camera to be from the head coaches point of view and I love it lol. If you turn off the commentary its like you're in the stadium!

Shady 🧊

1,481,515 views • 1 month ago

Florida offers freedom and opportunity. If you come here to escape the high tax, high regulatory states don’t try and turn this state into the state you fled from. Don’t New York Our Florida! Leave your leftist ideology and big spending ideas at the border.

Florida offers freedom and opportunity. If you come here to escape the high tax, high regulatory states don’t try and turn this state into the state you fled from. Don’t New York Our Florida! Leave your leftist ideology and big spending ideas at the border.

Blaise Ingoglia

50,332 views • 23 days ago

10K followers! Here the full video of the CPU decapping and the silicon doodles found, enjoy!

10K followers! Here the full video of the CPU decapping and the silicon doodles found, enjoy!

CPU Duke

18,706 views • 7 months ago

Here is a random performance test of WWE 2K18 running on the Switch 2 in Docked Mode. Full match between Bray Wyatt and Seth Rollins (CPU vs CPU) in the RAW arena. Essentially, the game runs exactly how it should have on the original Switch if it had been properly optimized and tested.

Here is a random performance test of WWE 2K18 running on the Switch 2 in Docked Mode. Full match between Bray Wyatt and Seth Rollins (CPU vs CPU) in the RAW arena. Essentially, the game runs exactly how it should have on the original Switch if it had been properly optimized and tested.

𝕾𝖙𝖆𝖙𝖚𝖘™

165,056 views • 2 months ago

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

The Pragmatic Engineer

13,258 views • 25 days ago

Nvidia announces the new RTX Spark, a new platform powered by the NX1 CPU, and shows off Spark laptops running 007 First Light and Forza 6. The CPU has 20 ARM based cores and a Blackwell RTX GPU with 6144 CUDA Cores. This is the same core count as a 5070, but with 128GB of unified LPDDR5X RAM memory sitting in the same package as the CPU and GPU. The entire Nvidia software stack is available, particularly CUDA, vital for AI. Nvidia's new laptops will likely be ideal for running local LLMs be cause the unified memory means you can load models up to 120-180B parameters (quantized). These laptops are expected to ship later this year and could become strong competitors to high-end MacBooks and even Mac Studios for local AI workloads, thanks to CUDA support and unified memory. Price is unannounced.

Nvidia announces the new RTX Spark, a new platform powered by the NX1 CPU, and shows off Spark laptops running 007 First Light and Forza 6. The CPU has 20 ARM based cores and a Blackwell RTX GPU with 6144 CUDA Cores. This is the same core count as a 5070, but with 128GB of unified LPDDR5X RAM memory sitting in the same package as the CPU and GPU. The entire Nvidia software stack is available, particularly CUDA, vital for AI. Nvidia's new laptops will likely be ideal for running local LLMs be cause the unified memory means you can load models up to 120-180B parameters (quantized). These laptops are expected to ship later this year and could become strong competitors to high-end MacBooks and even Mac Studios for local AI workloads, thanks to CUDA support and unified memory. Price is unannounced.

Grummz

30,573 views • 1 month ago

SMASH REMIX 2.0.1 HAS BEEN RELEASED!!! NEW STAGES, BUG FIXES, GAME MODE, CPU UPDATES AND MORE! PLEASE ENJOY SMASH REMIX 2.0.1! (I was given the honor to make the trailer)

SMASH REMIX 2.0.1 HAS BEEN RELEASED!!! NEW STAGES, BUG FIXES, GAME MODE, CPU UPDATES AND MORE! PLEASE ENJOY SMASH REMIX 2.0.1! (I was given the honor to make the trailer)

Maafia

146,515 views • 4 months ago

Deeply saddened at the state of Britain. Try and laugh where you can.

Deeply saddened at the state of Britain. Try and laugh where you can.

MinistryofWit

76,559 views • 1 year ago

For the last few weeks, I've been writing a multi-CPU single-board computer like explorer. I'm calling it CROSSWOZ (Hat tip to Woz and the WOZMON). Seven vintage CPU cores (6502, 65C02, Z80, 8080, 8085, 6809, 1802) share a 64K memory bus and the same WOZMON-style monitor. I can swap CPUs in place. It's got a mini-assembler per CPU, JMON-style debug, and animated paper-tape I/O. I'm pretty pleased with how it's turning out.

For the last few weeks, I've been writing a multi-CPU single-board computer like explorer. I'm calling it CROSSWOZ (Hat tip to Woz and the WOZMON). Seven vintage CPU cores (6502, 65C02, Z80, 8080, 8085, 6809, 1802) share a 64K memory bus and the same WOZMON-style monitor. I can swap CPUs in place. It's got a mini-assembler per CPU, JMON-style debug, and animated paper-tape I/O. I'm pretty pleased with how it's turning out.

mrdoornbos

14,998 views • 1 month ago

Dude, I haven’t touched my CPU since February. Getting back into it is crazy, but I just brought it back to life—synthesized and simulated. Can’t wait to hack on it again at the end of the month. It’s insanely fast and will be a Linux CPU. I’m super hyped. SystemVerilog forever.

Dude, I haven’t touched my CPU since February. Getting back into it is crazy, but I just brought it back to life—synthesized and simulated. Can’t wait to hack on it again at the end of the month. It’s insanely fast and will be a Linux CPU. I’m super hyped. SystemVerilog forever.

logic destroyer

50,026 views • 7 months ago