PDU Circuit Balancing Calculator

All your server is humming along. Everything’s working. Then some joker plugs in his high-density storage shelf. Lights start blinking, breakers trip, and panic ensues. Welcome to the classic home lab nightmare, and it almost always comes down to one thing: you balanced the outlets, but you ignored the power.

Use this page to make sure that never happens to you by converting your physical rack layout into a math problem before you lay a finger on a wire. It will estimate the remaining space (spare capacity), branch amps, and phase spread so you know exactly how close you’re pushing against the limit.

How to Plan Your Server Power Use

The first thing most folks do is count their plug. I’ve got 12 outlets, I’ve got 12 devices. Good enough! The second thing… Where most folks go wrong, is this: outlets aren’t power sources. They’re just physical connectors. If there are ten outlets on a PDU (power distribution unit) fed by one 20-amp breaker, you could easily be overloading the circuit if you fill all sockets up with even moderately-sized mini PCs.

But rather than thinking “socket count,” the tool makes you think “amps” and “watts.” You input number of devices and then how much each typically draws. It will tell you what that totals. Then it applies a derating factor, often 80 percent, that takes into account the sustained heat that comes from continuously loading circuits. For both longevity and safety reasons, you don’t argue with this step.

But the real fun start when you factor in redundancy. Most server are powered by two power supplies plugged into different power distribution units (PDUs), marked as A and B. During normal operations, the load is split equally. But what happens when Feed A fails? All of that juice flows over to Feed B. If Feed B has a 90 percent load, it’s going to trip immediately, shutting down half of your infrastructure. That’s exactly what failure scenario inputs on the calculator simulate. It shows you how much capacity remains for transferring load onto other circuits. And if it goes red, you know: You’re gonna need to rebalance before adding more gear. Seeing the issue on the screen is preferable than discovering it in the middle of a critical backup window.

Of equal importance is phase balance, whether you’re dealing with a split-phase residence or multiple three-phase environments. Placing all your high-draw loads onto one phase (e.g., Phase A) make the rest of your house a mess. It stresses the neutral conductor and fluctuates voltage on other legs. The tool allows you to model various assignments: round robin, manual skew, etc. Moving a high-draw GPU server from Phase A to Phase B has a ripple effect across the whole load. Perfect isn’t required; you want a nice balance. Less then ten percent variation between phases should be good enough for most labs.

Also: don’t trust nameplate specs. A server might say, “This server is only rated at 150 watts, but when I run a memory test or do a hard drive rebuild… ” No! Measure the steady state draw. Have an intelligent PDU? You can get a clamp meter cheaply and put it to work. Plug in, press button. If you know what your stuff draws, plug those real world numbers back into the tool. The site also includes some reference tables of common breaker sizes to get you started. However, the math comes from your gear. Run through the calculator first, confirm later with a meter.

And finally, account for expansion. You can’t tolerate any margin for error on a circuit that’s running near 100 percent. Put in a little smart UPS or network switch, and you’re over your head. Make sure there’s always plenty of headroom. 20 percent or so. That will guard against the effects of aging components, the inefficiency of wiring, and the ever-expanding set of gear you’ll add eventually.

Power balancing isn’t rocket science; it’s just good planning. When your servers are supposed to be up, they stays up. You’ve balanced your load, respected your breaker, and slept well at night. It should of been easier than this.