Performance Regression Hunting with Before/After Measurements
A disciplined before/after method for finding what slowed your service down, from capturing a baseline to bisecting the changes that caused it.
NetBay journal
21 practical Hardware & Performance articles from Netbay Engineering — written for operators running Linux and Windows VPS in India.
21 articles in this topic
A disciplined before/after method for finding what slowed your service down, from capturing a baseline to bisecting the changes that caused it.
A practical walkthrough that turns traffic forecasts into concrete CPU, RAM, and bandwidth numbers you can use to size a small web service now.
How interrupt handling, NUMA topology, and the Linux CPU scheduler behave inside a VPS, and exactly when you can realistically improve them.
What CPU credits and burst capacity really mean for throughput, and why sustained-load headroom matters far more than burst bragging rights.
A decision framework for whether to resize a VPS or fix the code instead, based on the actual shape of the bottleneck rather than guesswork.
How to measure IOPS and latency on virtualised solid-state storage, then tune the filesystem and block scheduler to match your access pattern.
Discover how dedicated CPU pinouts and enterprise SSD storage arrays yield 3x IOPS performance compared to traditional cloud VPS providers.
A hands-on guide to sampling CPU call stacks with perf and rendering them into flamegraphs that clearly expose the real hot functions in your code.
How to benchmark CPU, RAM, disk, and network on a VPS so the numbers are actually meaningful, and the common traps that make those numbers lie.
Learn what load average and the Unix CPU steal column really mean on a shared VPS, and how to tell noisy neighbours from real, unavoidable demand.
How fstrim and the discard mount option keep a virtualized SSD from wearing out or reporting phantom usage, with the guest-side commands to verify.
A repeatable drill that walks a slow VPS from the uptime command and top down to a hot function, so you fix the real bottleneck instead of chasing a symptom.