What's changed: New GH-100 Chapter 5 (monitoring usage & activity = analyze audit logs/API usage, SIEM streaming, admin vs Support triage and diagnostics, usage patterns [adoption/activity/underutilized features]; cost & performance optimization = usage reports for metered products [Actions minutes/storage/Packages/Copilot/GHAS], Actions cost optimization [filters/concurrency/caching/matrix/runner], reclaim unused seats, cut waste without lowering quality)
5.2Optimizing Cost and Performance
Understand interpreting usage reports for metered products and strategies for license and resource optimization—from an admin’s view, balancing cost and performance.
An admin’s job is turning data from monitoring (prior section) into cost and performance optimization. GitHub billing has both seats (licenses) and metered (Chapter 2); leaving waste unchecked balloons cost. GH-100 tests interpreting usage reports and optimization strategies.
5.2.1Usage reports for metered products
Common metered products are GitHub Actions minutes and storage, GitHub Packages storage, and Copilot/GHAS seats/usage. Admins interpret usage reports to see which orgs/repos consume the most cost and the trend (rising). For example, surging Actions minutes often stem from inefficient workflows (wasted runs, oversized matrices, no caching), pinpointing what to fix. Reports also support budgeting and chargeback (departmental allocation).
5.2.2License and resource optimization
Common optimizations: Licenses: reclaim unused/inactive seats (SCIM/EMU auto-free departed users, Chapter 1) and review over-provisioned plans. Actions cost: avoid unneeded runs (paths/branches filters), cancel stale runs via concurrency, avoid re-fetch via caching, keep matrices minimal, and right-size runners (shared with GH-200). Storage: shorten artifact/log retention. The principle is "cut waste without lowering coverage or quality"—avoid over-cutting (e.g., stopping needed tests).
Common: (1) Metered products = Actions minutes/storage, Packages, Copilot/GHAS; use usage reports to find high-consuming orgs/repos and trends (budget/chargeback). (2) Actions cost optimization = paths/branches filters, concurrency, caching, minimal matrices, runner sizing. (3) License optimization = reclaim unused seats (SCIM/EMU auto-frees departed users). (4) Principle: cut waste without lowering quality (avoid over-cutting).
Watch out: (1) Seat billing (fixed) and metered billing (Actions minutes, etc.) differ—look at both to optimize. (2) Stopping needed tests/scans to cut cost is counterproductive (hurts quality/security). (3) Unused seats left unchecked waste cost/compliance—reclaim regularly. (4) Catch usage-report trends (rising) early and act before a spike.
5.2.3Section summary
- Use usage reports for metered products (Actions minutes/storage, Packages, Copilot/GHAS) to track consumption/trends
- Optimize Actions cost via paths/branches filters, concurrency, caching, minimal matrices, runner sizing
- Optimize licenses by reclaiming unused seats (SCIM/EMU auto-frees departed users)
- Principle: cut waste without lowering quality; look at both seat and metered billing
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. GitHub Actions minutes are surging, ballooning cost. From reports, what cause is easy to pinpoint for fixing?
Q2. What should an admin do to optimize license cost?
Q3. Which combination is appropriate for Actions cost optimization?
Q4. Which correctly relates metered billing and seat billing?
Q5. What is an appropriate way to reduce storage cost (artifacts/logs)?
Q6. Which is the most appropriate principle for cost reduction?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.