Managing Resources To Lower Costs
summary
Jenkins uses donated JROG Artifactory and discovers 10 TB of storage and 50 TB/month bandwidth waste, costing thousands; access logs convert to SQL so queries reveal offenders and misconfigurations. Team reduces storage from 10 TB to under 2 TB without harming users, cuts 20+ TB of downloads by fixing clients, and blocks abusive IPs after cloud provider nonresponse. Key fixes: convert logs to SQL for forensic queries, cut storage from 10TB to <2TB, stop repeat downloads and block abusers.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:04Cluttered closets matter
- 2:10Clutter examples
- 3:15Jenkins storage mistake
- 4:19Cost of unmanaged storage
- 6:06Regulatory storage alternatives
- 6:27Docker storage and log leaks
- 8:13Bandwidth costs
- 10:24Fixing bandwidth waste
- 11:51Blocking abusive IPs
- 13:18Docker download limits
- 14:00Open source growth needs
- 15:27Call to action
- 16:30Stop caching artifacts
- 17:14Tragedy of the commons
- 18:01Monitoring resources
related talks
10mReducing infrastructure cost during development and in production
35mOptimizing Your CI: Lessons Learned from a Successful Jenkins Rebuild
20mLogging in the Age of Cost-Cutting
32mWriting Performance User Plugins for an HA Environment
50mPerformance: Avoiding Pitfalls, Diagnosing Issues & Scaling for Growth
47mCost optimization
41mScaling Observability: From Chaos to Clarity with Open Source Tools
32mNavigating a Mined World: Repositories, Registries and Artifact Storages.