Loading video...

Video Failed to Load

Go Home

You asked for it, so here it is. Visualizing CPU cache speeds relative to RAM. Cache optimization is important too!

BenjDicken's profile picture

Ben Dicken

51,046 subscribers

1,474,872 views • 2 years ago •via X (Twitter)

Science & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Some of the biggest news today is Cloudflare Worker's Cache. So I built this small catalog to experience it. It allows you to purge the cache for certain pages, or the entire catalog. It also shows you the exact caching headers used. See it in action or try it yourself:
0:16

Some of the biggest news today is Cloudflare Worker's Cache. So I built this small catalog to experience it. It allows you to purge the cache for certain pages, or the entire catalog. It also shows you the exact caching headers used. See it in action or try it yourself:

Jilles Soeters

17,920 views • 3 months ago

Submitted Easy Vertex Anim for #UE5.8 too. You can create pivot painter 2 effects and bake chaos cache to vat, 100% NO AI, check it out!
0:16

Submitted Easy Vertex Anim for #UE5.8 too. You can create pivot painter 2 effects and bake chaos cache to vat, 100% NO AI, check it out!

Inu Games

10,373 views • 4 months ago

MeidasTouch It was still in my cache
0:19

MeidasTouch It was still in my cache

DANNYonPC

11,097 views • 2 months ago

WanGP's latest MiniMax H3 update is huge: - Way faster Generation - 2X faster Ref2VA - Lower-RAM & new accelerators - Long videos with smoother visual/audio transitions. - Huge speed gains with Sol-Attention, First Block Cache, etc. And Pinokio launcher is optimized for it 👇
0:14

WanGP's latest MiniMax H3 update is huge: - Way faster Generation - 2X faster Ref2VA - Lower-RAM & new accelerators - Long videos with smoother visual/audio transitions. - Huge speed gains with Sol-Attention, First Block Cache, etc. And Pinokio launcher is optimized for it 👇

cocktail peanut

61,351 views • 2 months ago

A lot of people asked me to post FOOTage of Iuno's burst It features her, you guessed it, feet So here it is Enjoy!
0:16

Sensitive content

A lot of people asked me to post FOOTage of Iuno's burst It features her, you guessed it, feet So here it is Enjoy!

Geralt of Goonia

261,127 views • 6 months ago

cache is out so use this easy b site utility and win the round (hopefully)
0:13

cache is out so use this easy b site utility and win the round (hopefully)

mirage instant window smoke dritter spawn

102,149 views • 6 months ago

Want the latest, flashiest skins? Lucky Cache is here for you every week! Every Friday to Sunday, Step into the Lucky Cache and challenge destiny! (level 80 needed) 🎁 One free draw every week A single draw could change everything and rewards can refresh 3 times a week — are you ready? Luck doesn't wait!
0:16

Want the latest, flashiest skins? Lucky Cache is here for you every week! Every Friday to Sunday, Step into the Lucky Cache and challenge destiny! (level 80 needed) 🎁 One free draw every week A single draw could change everything and rewards can refresh 3 times a week — are you ready? Luck doesn't wait!

Call of Odin's Chosen

121,198 views • 10 months ago

cache-cache à paris
0:17

cache-cache à paris

doodles

126,930 views • 1 year ago

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.
0:14

Day 11/90 of Inference Engineering How does vLLM work and how is it used in production? Before we discuss how vLLM works internally, it helps to understand what vLLM is. At a high level, vLLM is an inference engine that is designed to serve LLMs to thousands of concurrent users efficiently while managing scarce compute and memory. The goal for vLLM is to maximize throughput and minimize latency; optimizing for the best inference economics and experience for end users. With every request from the end user, it eventually ends up in the engine core, gets scheduled alongside other requests from other concurrent users, executes on the GPU, and updates the KV cache with the new key and value vectors, and streams the tokens back to the user. The Scheduler decides what requests should execute next while continuously batching requests together to maximize GPU utilization. Continuous batching is an inference optimization that allows new requests to join a running batch as other requests finish generating tokens. This helps with keeping the GPU utilization high instead of letting it sit idle waiting for an entire batch to complete generating. After the scheduler dispatches the selected batch to the Model Executor, the Model Executor prepares the tensors and metadata required for inference, retrieves each request’s block table from KV Cache Manager, launches the optimized transformer forward pass on the GPU, computes the logits, updates the KV cache with the new key and value vectors, and finally returns the results for sampling and streaming. The KV Cache Manager uses the PagedAttention memory layout to allocate fixed-size cache blocks on demand and maintains a Free Block Queue on the CPU that tracks which blocks in the GPU’s Paged KV Cache are currently free. When a request needs additional KV cache space, the KV Cache manager takes a free block from the queue and assigns it to that request, thus avoiding an expensive search through GPU memory for available cache blocks. All of these components form the core of vLLM’s inference engine. The Scheduler determines what requests are executed, the Model Executor determines how those requests are executed, the KV Cache Manager determines where each request’s KV cache lives using the PagedAttention Memory Layout. This architecture enables vLLM to serve thousands of concurrent requests with high throughput, low latency, and efficient GPU memory utilization. Heres a little animation that visualizes everything! - I've also completed the forward pass for my mnist.c project. I had a nice chat with shrey birmiwal, such a knowledgeable guy. Excited to learn more about vLLM and implement a tiny-vLLM one day.

max fu

71,124 views • 3 months ago

Seniors discussing Architecture: Redis vs In-Memory Cache Meanwhile, the Vibe Coder😂 wait for it
0:12

Seniors discussing Architecture: Redis vs In-Memory Cache Meanwhile, the Vibe Coder😂 wait for it

Mashood K

152,831 views • 4 months ago

RAM and CPU is DEAD ☠️
0:12

RAM and CPU is DEAD ☠️

kapilansh

928,280 views • 2 months ago

Is it too much for you to handle?
0:15

Sensitive content

Is it too much for you to handle?

Fat Ass Sid

16,792 views • 10 days ago

RAM and CPU is DEAD ☠️😱
0:12

RAM and CPU is DEAD ☠️😱

Know Your Computer 💻

16,665 views • 2 months ago

🚨 Today I published my own Stream Deck plugin on @Elgato Marketplace . I call it SimpleStats. It's a very lightweight plugin for viewing CPU usage, Ping, Net Throughput, GPU temps, even what is using up all your RAM!!!!!!! The most important part for me: Everything is included.
0:19

🚨 Today I published my own Stream Deck plugin on @Elgato Marketplace . I call it SimpleStats. It's a very lightweight plugin for viewing CPU usage, Ping, Net Throughput, GPU temps, even what is using up all your RAM!!!!!!! The most important part for me: Everything is included.

Brett

114,702 views • 6 months ago

But the KV cache is created for each transformer layer. By sending each layer’s KV cache after it’s computed, we overlap communication with computation. We stream the KV cache and hide the network delay. We achieve a 4x speedup in prefill & 3x in decode, with 0 network delay.
0:11

But the KV cache is created for each transformer layer. By sending each layer’s KV cache after it’s computed, we overlap communication with computation. We stream the KV cache and hide the network delay. We achieve a 4x speedup in prefill & 3x in decode, with 0 network delay.

EXO Labs

50,617 views • 1 year ago

s1mple hitting awp clips on Cache what year is this 😍
0:17

s1mple hitting awp clips on Cache what year is this 😍

BC Game Esports

91,966 views • 3 months ago

TONS of you asked for it. So here you go. The Caliendo Cut. #madden
0:18

TONS of you asked for it. So here you go. The Caliendo Cut. #madden

Frank Caliendo

839,040 views • 4 days ago

being able to pop into a level at an exact location is so important and so common, you NEED a button for it.
0:17

being able to pop into a level at an exact location is so important and so common, you NEED a button for it.

thomas "noio" vandenberg

20,938 views • 7 months ago