Not every hyperparameter deserves equal tuning effort. Sensitivity analysis measures how much a model's validation loss changes when you perturb one hyperparameter at a time (an "OAT" — one-at-a-time — sweep) while holding the rest fixed. Parameters whose perturbation causes large swings in loss are critical: they deserve careful search. Parameters that barely move the loss can be fixed at a sensible default and skipped in expensive tuning runs.
In practice, learning rate is consistently the most sensitive hyperparameter across architectures — studies on tuning budgets (e.g. Bergstra & Bengio's random search work) found that a handful of parameters typically account for most of the variance in model performance, which is exactly why sensitivity analysis is used to prioritize where limited compute for tuning should go.
A 3D validation-loss landscape over learning rate and dropout, paired with a live tornado chart that ranks four hyperparameters by how much perturbing each one changes the loss.
One-at-a-time (OAT) sensitivity: each tornado bar is the change in validation loss when a single hyperparameter is nudged by a set percentage while the others stay fixed — the standard way to spot which knobs matter most.
Move the learning rate and dropout sliders to slide the glowing marker across the loss surface. Change batch size, weight decay or the perturbation size and watch the tornado bars and "most critical" parameter update live.
Sensitivity analysis lets teams spend their limited tuning budget on the two or three hyperparameters that actually move performance, while leaving low-sensitivity ones at sane defaults.