[portfolio] 📊 Portfolio Dashboard - 2026-04-06 #24848
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-04-07T09:51:00.265Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Overview
Analysis of 317 workflow runs over 3 days (Apr 4–6, 2026). Total spend: $51.39 (~$17.13/day). The portfolio has one dominant cost driver —
Smoke Claudeat $18.37 (36% of spend) — and a reliability concern with 38.8% of runs completing with errors. Most high-error workflows have zero token cost (smoke/integration tests), so wasted spend is concentrated in ~$6.21 of identifiable failures.Visual Summary
Cost Trends (Apr 4–6)
Key Insights:
Top Cost Drivers
Top 3 workflows account for ~47% of total cost:
Smoke Claude— $18.37 (green: 14% error rate, triggered by PRs + schedule)Go Logger Enhancement— $3.76 (red: 50% error rate)Sergo - Serena Go Expert— $1.99 (green: 0% errors)Failure Analysis
Wasted Spend on High-Error Workflows: ~$6.21
CI Cleaner,Smoke Gemini,Smoke Codex,AI Moderator)Overall Run Distribution
💰 Cost Reduction Opportunities
Total Identifiable Savings: ~$3.76–$9.50/month (7–18% reduction)
Strategy 1: Fix High-Error Costly Workflows — $3.76 wasted/3 days
These workflows have both significant cost AND high error rates:
Go Logger EnhancementDaily Documentation UpdaterCopilot Agent Prompt Clustering AnalysisStep Name AlignmentFix: Investigate and fix root causes of failures. These workflows appear to be one-time runs or early-stage, so errors suggest broken implementations rather than systematic issues.
Potential savings: ~$3.43/period if error rates drop to ~0%
Strategy 2: Address High-Failure Zero-Cost Workflows — Reliability Risk
These workflows run frequently but fail constantly. While currently zero token-cost (they fail before incurring AI costs), they represent infrastructure waste and reliability risk:
AI ModeratorSmoke CodexIssue MonsterChangeset GeneratorSmoke GeminiCI CleanerGitHub Remote MCP Authentication TestFix: Disable or pause
Smoke Gemini,Smoke Codex,CI Cleaner, andGitHub Remote MCP Authentication Testuntil underlying engine/auth issues are resolved. ReduceIssue MonsterandAI Moderatorschedule frequency while debugging.Potential savings: Reduced CI minutes + faster failure detection
Strategy 3: Reduce Smoke Claude Scheduling — $9.50+/month
Smoke Claudeis the single largest cost driver at $18.37 over 3 days. It runs on both PR events AND schedule:Recommendation: Review whether smoke tests need to run on EVERY PR vs. only on specific label or draft-to-ready transitions. If reduced from every PR to labeled PRs only, estimated savings: 30–50% of smoke test cost.
Potential savings: ~$3–9/month (conservative estimate based on 3-day window)
🎯 Priority Actions
Smoke Gemini,Smoke Codex, andGitHub Remote MCP Authentication Test(100% failure rate, running 3x/day)Go Logger Enhancementfailure root cause ($1.88 wasted on 2 runs, 50% failure)AI ModeratorandChangeset Generator(96%/88% failure rates, very high run frequency)Smoke Claudeto reduce unnecessary runs (top cost driver)Daily Documentation UpdaterandDaily Copilot Token Usage Audit(high error rates on daily schedules)📈 Data Quality
Methodology: Analysis based on pre-downloaded execution data from
gh aw logs. Costs calculated from actual token usage tracked in episodes. Error rate based onerror_count > 0per run.References:
Beta Was this translation helpful? Give feedback.
All reactions