Skip to content

Fix execution unit in task-counting doc: seconds not minutes - #25

Open
jwmossmoz wants to merge 1 commit into
mainfrom
fix/derived-task-summary-execution-seconds
Open

jwmossmoz wants to merge 1 commit into
mainfrom
fix/derived-task-summary-execution-seconds

Conversation

@jwmossmoz

Copy link
Copy Markdown
Collaborator

derived_task_summary.execution is wall-clock seconds, not minutes. The azure-cost-analysis reference doc (taskcluster-task-counting.md) says minutes in three places.

Verified against May 2026 data: gecko-t win11 p50 is ~1409 s (~23 min/task). If the unit were minutes, p50 would be ~23 hours, which is impossible given task deadlines (observed max ~7519 s ≈ 2.1 h). Treating the column as minutes makes task-hours off by 60x in any cost-per-task or utilization analysis.

Changes:

  • Column note: execution (minutes) → (seconds, wall-clock task runtime)
  • Sample query alias: avg_exec_minutesavg_exec_seconds
  • Caveat: divide by 3600 for hours; outlier filter is < 86400 s (24 h), not < 1440 min

Doc-only change.

derived_task_summary.execution is wall-clock seconds, not minutes. Verified
May 2026: gecko-t win11 p50 is ~1409 s (~23 min/task); as minutes that would be
23 h, which is impossible given task deadlines. Using minutes makes task-hours
off by 60x in cost-per-task analysis. Updates the column note, the sample
query alias, and the outlier-filter caveat (86400 s, not 1440 min).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant