---
title: "Discussion on \"Desired = max: why our batch fleet never scaled in\" | Hashnode"
description: "Discussion on \"Desired = max: why our batch fleet never scaled in\". Some of our batch jobs ran for up to 14 hours. Every deploy killed the ones that were running, and nobody ran them again.\nI didn't start there, though. I started with a CPU graph and an idea for savin"
url: "https://hashnode.com/posts/desired-max-why-our-batch-fleet-never-scaled-in/6af1eae359ac62cac9cabff4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Desired = max: why our batch fleet never scaled in](https://devops-stories.hashnode.dev/desired-max-why-our-batch-fleet-never-scaled-in?utm_source=hashnode&utm_medium=feed)

Some of our batch jobs ran for up to 14 hours. Every deploy killed the ones that were running, and nobody ran them again. I didn't start there, though. I started with a CPU graph and an idea for savin

2d ago · 11 min read · devops-stories.hashnode.dev  
Read the article

## Written by

[Shad Reza](https://hashnode.com/@shadreza)

@shadreza

  
[View profile](https://hashnode.com/@shadreza)

scaling ideas, one dev story at a time.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.