Back to videos

Slack vs. Waste

Waste is when resources are deeply over-provisioned, underutilized, or not utilized at all. Slack appears like the same thing, but you create it with purpose. It's important to understand the difference to drive costs down.
2 min
play_arrow
Summary

What is the difference between slack and waste in production ops?

Waste is when resources are deeply over-provisioned, underutilized, or not utilized at all.

On the other hand, slack appears like the same thing, but you create it with purpose.

Here’s why we create slack:

You can't operate your systems at 100% because you need to deal with:
- variability in demand, such as usage spikes
- background activities that may get prioritized out (you will have to to catch up with them later in foreground latency)
- disk, node, and network failures, where you need to rotate demand to things that are still around

So slack is the excess resources you keep around to deal with unexpected demands, activity loads, and failures.

In upcoming videos, I’ll talk about how I’ve reduced both slack and waste in the past.

Transcript

View more Shoreline videos

Looking for more? View our most recent videos
5 min
How Shoreline Helps You Get a 4 9’s SLA
Since we’re all sitting on similar infrastructure, if someone solves an issue, everyone should be able to benefit from it. That’s one of the ways we help our customers to save time, reduce errors, and get to a four 9’s SLA.
2 min
Our Community-Driven Library of Shared Automations
We're all sitting on the same infrastructure in Production Ops, but build our systems as if we’re starting new. Insane! That's why Shoreline Op Packs are available for free.
3 min
Is Automation Too Time-Consuming?
Automation takes us too much time. The problem with this approach is that 48% of incidents are straightforward and repetitive. Don't have people fix them manually. Teach the computer how to do it.