AWS Glue Job DPU Rightsizing
Glue bills per DPU-hour, so DPUs allocated beyond what the job's parallelism can use are billed for the whole run and do no work.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce DPUs on the Glue job. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight resizes it to the recommended tier, then checks the change took.
- Applies to
- Glue Jobs on AWS
- The fix, by hand
- Open the Glue job and review the current MaxCapacity (DPU count).
- Check the Glue job run history for executor utilisation.
- Enable Glue job metrics and review glue.driver.ExecutorPool.numberAllExecutors vs. numberActiveExecutors.
- Reduce MaxCapacity incrementally (e.g., by 25%) and compare run times.
- Enable Glue auto-scaling if available for the job type to let AWS optimise DPUs dynamically.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-098- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.