Videos / DevOps

Episode 2 of 14 · DevOps, end to end

VMs and bare metal: what a machine actually is

Chapters

1. Take the lid off0:00
2. Cores, then threads0:15
3. The memory ladder0:32
4. Fill every channel0:48
5. Two sockets, NUMA1:05
6. The drives underneath1:22
7. A convincing lie1:40
8. Type one, type two1:58
9. Why this used to be hard2:18
10. Guest mode, and exits2:37
11. The second page table2:55
12. Virtio stops the act3:15
13. A ticket, not silicon3:33
14. Overcommit3:50
15. Wide guests wait longer4:08
16. The st column4:26
17. The mystery, from inside4:41
18. What to do about steal4:58
19. The balloon5:15
20. Time is elastic, memory is not5:30
21. One device, three backings5:48
22. Two caches, one flush6:06
23. A switch made of software6:23
24. Speed costs mobility6:41
25. A menu with prices6:59
26. The word on the invoice7:18
27. Scratch space, or state7:36
28. The ceiling you own7:54
29. The neighbours8:11
30. Fill the host, or offload8:27
31. Where is the wall8:45
32. A container is a process9:02
33. The chip enforces this one9:20
34. The whole machine, whole problem9:37
35. The line moved recently9:55
36. Isolation, then utilisation10:14
37. What a machine is10:31

VMs and bare metal: what a machine actually is. Take the lid off a server and there is no cloud in there. There are sockets holding processors, sticks of memory, a network card, and drives. Everything you will ever run is that h

Mark as watchedSaved in this browser only.