Skip to main content

Performance Tutorials & Guides

49 articles tagged with Performance.

A field-tested workflow for finding which process burns your CPU and whether the time is user, system, or iowait.
••2 months ago

Tracking Down High CPU on Linux

A field-tested workflow for finding which process burns your CPU and whether the time is user, system, or iowait.

KU
Kiril Urbonas·56
Read article
Load average counts more than CPU demand, so a high number needs a diagnostic path before you reach for a fix.
••2 months ago

Diagnosing High Load Average on Linux

Load average counts more than CPU demand, so a high number needs a diagnostic path before you reach for a fix.

KU
Kiril Urbonas·42
Read article
A practical method for reading free, top, and ps correctly so you attribute Linux memory to a real cause instead of guessing.
••2 months ago

Find What's Eating Your RAM on Linux

A practical method for reading free, top, and ps correctly so you attribute Linux memory to a real cause instead of guessing.

KU
Kiril Urbonas·41
Read article
When a process hits its file descriptor ceiling everything breaks at once; here is how to find the real limit and raise it correctly.
••2 months ago

Fix "Too Many Open Files" on Linux (ulimit)

When a process hits its file descriptor ceiling everything breaks at once; here is how to find the real limit and raise it correctly.

KU
Kiril Urbonas·55
Read article
The edge is fast because it's constrained. This is the decision map for what belongs at the edge, what belongs at origin, and how compute, data, caching, and auth fit together.
••2 months ago

The Edge Computing Playbook — What to Run at the Edge (and What Not To)

The edge is fast because it's constrained. This is the decision map for what belongs at the edge, what belongs at origin, and how compute, data, caching, and auth fit together.

KU
Kiril Urbonas·33
Read article
Edge code runs in hundreds of PoPs, lives for milliseconds, and gives you no shell. Here's how we get logs, traces, and metrics out of it anyway.
••3 months ago

Observability for Edge Functions — Logs, Traces, and Metrics

Edge code runs in hundreds of PoPs, lives for milliseconds, and gives you no shell. Here's how we get logs, traces, and metrics out of it anyway.

KU
Kiril Urbonas·12
Read article
Verifying signed tokens at the edge with WebCrypto blocks bad traffic early and saves a full origin hop. Here's the pattern we ship, and the traps.
••3 months ago

Edge Auth — Validating JWTs Without Origin Round-Trips

Verifying signed tokens at the edge with WebCrypto blocks bad traffic early and saves a full origin hop. Here's the pattern we ship, and the traps.

KU
Kiril Urbonas·18
Read article
A request leaving a laptop somehow lands on a server 20ms away. Here is what actually decides which point of presence answers.
••3 months ago

Anycast and Geo-Routing — How Requests Reach the Nearest PoP

A request leaving a laptop somehow lands on a server 20ms away. Here is what actually decides which point of presence answers.

KU
Kiril Urbonas·36
Read article
Evicted pods are the kubelet telling you a node ran out of something. Here's how to read the signal, stop the bleeding, and keep it from happening again.
••3 months ago

Fixing Evicted Pods and Node Pressure in Kubernetes

Evicted pods are the kubelet telling you a node ran out of something. Here's how to read the signal, stop the bleeding, and keep it from happening again.

KU
Kiril Urbonas·36
Read article
Exit 137 usually means the kernel shot your container for eating too much memory. Here's how to confirm the OOM kill and stop it happening again.
••3 months ago

Fix Docker Exit Code 137 (Container Killed / OOM)

Exit 137 usually means the kernel shot your container for eating too much memory. Here's how to confirm the OOM kill and stop it happening again.

KU
Kiril Urbonas·56
Read article
A pod dies, restarts, dies again, and the events say OOMKilled. Here is what exit code 137 actually means and how to stop the loop for good.
••3 months ago

How to Fix OOMKilled (Exit Code 137) in Kubernetes

A pod dies, restarts, dies again, and the events say OOMKilled. Here is what exit code 137 actually means and how to stop the loop for good.

KU
Kiril Urbonas·42
Read article
Buffered SSR makes users wait for the slowest query before they see anything. Streaming from the edge flips that — send the shell now, fill the gaps as data lands.
••3 months ago

Streaming SSR at the Edge — RSC and HTML Streaming

Buffered SSR makes users wait for the slowest query before they see anything. Streaming from the edge flips that — send the shell now, fill the gaps as data lands.

KU
Kiril Urbonas·28
Read article