Power Saving in Proxmox: What Works, What Doesn’t
For many homelab enthusiasts, there’s a moment when the math clicks. You’re running Proxmox 24/7 on a modest mini PC or old desktop, and…
Power Saving in Proxmox: What Works, What Doesn’t
For many homelab enthusiasts, there’s a moment when the math clicks. You’re running Proxmox 24/7 on a modest mini PC or old desktop, and one day you plug it into a smart outlet or check your power meter. The number staring back at you is small — maybe 40 or 50 watts — but it’s always there, ticking up every hour of every day.
Do the yearly calculation and the “cheap little home server” turns out to be costing you €150–€200 just to sit idle. That’s before you add workloads, before you start spinning up VMs, before you even think about running GPUs or RAID arrays. Suddenly, those low-power tweaks aren’t just for fun — they’re the difference between a reasonable experiment and a costly hobby.

And that’s where things get tricky: power saving on Proxmox isn’t straightforward. Some changes make a huge difference, cutting idle draw in half. Others are unstable, hardware-dependent, or flat-out don’t work. After combing through guides, experiments, and user experiences, here’s a breakdown of what actually works, what doesn’t, and where the trade-offs land.
What Actually Works
1. Ditching or Disabling the GPU
If you don’t need a GPU for gaming or machine learning, pull it. A dedicated graphics card can idle at 10–30W, which is basically lighting money on fire if you’re only running VMs and containers.
For setups where you do need the GPU (say for a passthrough VM), the trick is blacklisting the driver in Proxmox and passing the whole PCI bus through. That way, the GPU isn’t sucking down power while idle. Users running Nvidia cards confirm that once bound to vfio-pci, the GPU drops into low-power states. Some even undervolt and enable persistence mode to get idle draw down to just 4W.
Verdict: Big savings, reliable results. If your server doesn’t need a GPU, removing or isolating it is step one.
2. Switching to SSDs
Hard drives aren’t just slower — they’re power hogs compared to SSDs. A spinning disk might draw 5–7W continuously, and if you’ve got a stack of them for ZFS or backups, those watts add up.
SSDs, especially NVMe drives, sip power in comparison and deliver far better performance. Some users report that just moving from HDD-based storage pools to all-SSD setups cut idle consumption by 10W or more.
For pure backups, HDDs still make sense, but keep them off your main workload. Set spin-down timers (hdparm -S) for drives you rarely use. Just note that in ZFS pools, random I/O can keep them spinning no matter what.
Verdict: Works well if you can afford SSDs. HDD spin-down is hit-or-miss depending on workload.
3. Tuning CPU Power Profiles
Proxmox (and Linux in general) defaults to a performance governor, which keeps CPUs running at higher frequencies even when idle. Changing this makes a night-and-day difference.
With linux-cpupower and tuned, you can shift cores into powersave mode:
apt install linux-cpupower tuned powertop
cpupower frequency-set -g powersave
tuned-adm profile powersave
This lets CPUs drop into deeper sleep states, especially on newer Intel chips with efficiency cores. Community reports suggest this can shave 10–15W at idle, particularly if combined with other tweaks like disabling unused peripherals.
Verdict: Huge win, and survives reboots if configured properly.
4. Efficient Network Interfaces
Network cards can be sneaky power drains. High-performance 10GbE adapters are notorious for preventing CPUs from entering deep sleep states. Unless you really need multi-gig speeds, stick with 1GbE or enable Energy-Efficient Ethernet (EEE):
ethtool --set-eee enp12s0 eee on
ethtool -C enp12s0 rx-usecs 125
There’s also a major catch with 2.5GbE NICs from Intel and Realtek. By default, their kernel drivers keep power saving disabled, locking CPUs into shallow C-states and wasting energy. Switching to Realtek’s R8125 DKMS driver fixes this, cutting idle draw from 24–25W down to 12–13W in some cases.
Verdict: Can cut power use in half on certain setups. Worth the hassle of compiling drivers.
5. Modern Laptop-Class CPUs
Sometimes, the biggest power saver is a hardware upgrade. Desktop chips from a few years ago can idle surprisingly high, while newer laptop-class CPUs — especially Intel 12th and 13th gen with P-cores and E-cores — are built for efficiency.
One user swapped an old i3–9100 mini PC (~45W idle) for a Minisforum NPB7 with a 13th-gen CPU (~20W idle). Same workloads, less than half the power.
Verdict: If you’re serious about 24/7 uptime, a modern laptop-class system pays for itself in electricity savings.
What Doesn’t Really Work
1. Powertop Auto-Tune
On paper, powertop --auto-tune looks like the holy grail: one command to optimize every device’s power state. In practice? It’s risky.
- Powertop hasn’t been updated since 2022.
- Auto-tune can cause instability on some systems.
- It was designed with Intel CPUs in mind, with mixed results on AMD.
You can borrow some of its recommended settings and apply them manually, but running it as a blanket solution is asking for crashes.
Verdict: Not recommended as-is. Manual tuning works better.
2. HDD Spin-Down with ZFS
In theory, spinning down idle drives saves a few watts each. In practice, ZFS constantly flushes cache to disk, waking drives up every few seconds. Users report it’s “hit and miss” at best, and can actually stress drives with frequent spin-up cycles.
For bulk storage that’s not touched often (like a cold backup pool), spin-down can help. But for anything active, it’s more hassle than it’s worth.
Verdict: Tiny gains, not worth the wear and tear in most cases.
3. Using Servers as Heaters
One commenter joked that “in winter, every watt you spend on power isn’t wasted, it just heats your home.” And that’s technically true — but resist the temptation to think of servers as efficient heaters.
A resistive load (like a PC) converts electricity into heat at 1:1. A heat pump, by comparison, can be 3x more efficient, delivering three units of heat per unit of electricity. So while your homelab might keep your office cozy, it’s an expensive space heater.
Verdict: Cute idea, terrible economics.
The Gray Areas
Active State Power Management (ASPM)
ASPM lets PCIe devices enter low-power states. Some boards support it, some don’t. Some enable it by default, others bury it in BIOS menus. And in some cases, enabling it causes instability.
There are community scripts like AutoASPM, which attempt to tune settings dynamically. For certain systems, it can be the single biggest power saver. For others, it’s a source of crashes and kernel panics.
Verdict: Potentially great, but trial and error.
Scheduling Server Downtime
If your Proxmox box doesn’t need to be online 24/7, scheduling nightly shutdowns and wake-on-LAN can save serious energy. Shaving even 8–12 hours of runtime per day could cut your bill by a third.
But for many homelabbers, the point of running a server is to have it always on. That makes scheduled downtime more of a niche solution than a general fix.
Verdict: Works well, but not practical for everyone.
What the Numbers Look Like
The community anecdotes line up pretty clearly:
- Baseline old hardware: 40–60W idle
- Tweaked with CPU powersave, NIC drivers, SSDs: 20–30W idle
- Modern laptop-class CPU builds: 10–20W idle
That means a careful build and a few software tweaks can realistically cut your yearly server cost in half — or more. At €0.38/kWh, dropping from 50W to 20W saves about €100 per year. Multiply that across multiple homelab machines, and the savings are substantial.
Power saving in Proxmox is less about a magic setting and more about stacking small wins. Swap HDDs for SSDs. Use laptop-class CPUs. Switch network drivers. Tune your CPU governor. Each one might only save a few watts, but together, they transform a power-hungry tower into a low-draw, always-on lab that doesn’t feel like a guilty pleasure every time the utility bill arrives.
Some tweaks (like ASPM or powertop auto-tune) are a gamble, and some “savings” (like HDD spin-down) aren’t worth the trade-off. But the big picture is clear: with the right mix of hardware and software changes, Proxmox homelabs can go from 50W space heaters to sleek 20W micro-servers — and that’s the difference between an expensive hobby and a sustainable one.
메타데이터
- post_id
- ea96559258cd
- slug
- power-saving-in-proxmox-what-works-what-doesnt-ea96559258cd
- url
- https://medium.com/@PlanB./power-saving-in-proxmox-what-works-what-doesnt-ea96559258cd
- canonical_url
- https://medium.com/@PlanB./power-saving-in-proxmox-what-works-what-doesnt-ea96559258cd
- author_url
- https://medium.com/@PlanB.
- status
- ok
- fetched_at
- 2026-07-23 15:42:54