
Sign up to save your podcasts
Or


I deal with a lot of servers at work, and one thing everyone wants to know about their servers is how close they are to being at max utilization. It should be easy, right? Just pull up top or another system monitor tool, look at network, memory and CPU utilization, and whichever one is the highest tells you how close you are to the limits.
For example, this machine is at 50% CPU utilization, so it can probably do twice as much of whatever it's doing.And yet, whenever people actually try to project these numbers, they find that CPU utilization doesn't quite increase linearly. But how bad could it possibly be?
To answer this question, I ran a bunch of stress tests and monitored both how much work they did and what the system-reported CPU utilization was, then graphed the results.
Setup
I vibe-coded a script that runs stress-ng [...]
---
Outline:
(01:06) Setup
(02:01) Results
(02:07) General CPU
(02:45) 64-bit Integer Math
(03:19) Matrix Math
(04:08) Whats Going On?
(04:11) Hyperthreading
(04:54) Turbo
(05:33) Does This Matter?
The original text contained 2 footnotes which were omitted from this narration.
---
First published:
Source:
---
Narrated by TYPE III AUDIO.
---
Images from the article:
Apple Podcasts and Spotify do not show images in the episode description. Try Pocket Casts, or another podcast app.
By LessWrongI deal with a lot of servers at work, and one thing everyone wants to know about their servers is how close they are to being at max utilization. It should be easy, right? Just pull up top or another system monitor tool, look at network, memory and CPU utilization, and whichever one is the highest tells you how close you are to the limits.
For example, this machine is at 50% CPU utilization, so it can probably do twice as much of whatever it's doing.And yet, whenever people actually try to project these numbers, they find that CPU utilization doesn't quite increase linearly. But how bad could it possibly be?
To answer this question, I ran a bunch of stress tests and monitored both how much work they did and what the system-reported CPU utilization was, then graphed the results.
Setup
I vibe-coded a script that runs stress-ng [...]
---
Outline:
(01:06) Setup
(02:01) Results
(02:07) General CPU
(02:45) 64-bit Integer Math
(03:19) Matrix Math
(04:08) Whats Going On?
(04:11) Hyperthreading
(04:54) Turbo
(05:33) Does This Matter?
The original text contained 2 footnotes which were omitted from this narration.
---
First published:
Source:
---
Narrated by TYPE III AUDIO.
---
Images from the article:
Apple Podcasts and Spotify do not show images in the episode description. Try Pocket Casts, or another podcast app.

26,392 Listeners

2,423 Listeners

8,623 Listeners

4,151 Listeners

92 Listeners

1,585 Listeners

9,830 Listeners

89 Listeners

488 Listeners

5,469 Listeners

16,035 Listeners

536 Listeners

133 Listeners

96 Listeners

502 Listeners