alamb commented on issue #25088:
URL: https://github.com/apache/datafusion/issues/25088#issuecomment-6323745951

   Over the last 24 hours, according to my data, the projects use the following 
amount of github hosted runner time (this doesn't include RunsOn hosted runners)
   
   airflow is using approximately **20x** more CI runner time than DataFusion. 
   
   
   * apache/airflow **112.9 days**
   * apache/beam **50 days**
   * apache/kvrocks **17.4 days**
   * apache/arrow-rs **5.8 days**
   * apache/datafusion **5.6 days**
   
   I am gathering data for other projects as well
   
   <details>
   ```
   1406 runs of apache/airflow created since 2026-10-20T16:22:06Z (24.0 h 
window)
   jobs loaded: 1336 runs from cache, 67 from the API, 3 failed  (cache: 
gh-runner-usage-cache)
   
   conclusion     jobs  share runner-min runner-days
   success       18405  57.1%     162619       112.9
   skipped       10658  33.0%          0         0.0
   cancelled      2744   8.5%      15384        10.7
   failure         276   0.9%       3487         2.4
   in_progress     168   0.5%          0         0.0
   queued            1   0.0%          0         0.0
   total         32252            181489       126.0
   
   average concurrent jobs over the window: 126
   
   
   117 runs of apache/kvrocks created since 2026-10-20T16:23:09Z (24.0 h window)
   jobs loaded: 99 runs from cache, 18 from the API, 0 failed  (cache: 
gh-runner-usage-cache)
   
   conclusion     jobs  share runner-min runner-days
   success         713  79.3%      25075        17.4
   cancelled       100  11.1%       1778         1.2
   in_progress      37   4.1%          0         0.0
   failure          25   2.8%        378         0.3
   skipped          24   2.7%          0         0.0
   total           899             27231        18.9
   
   average concurrent jobs over the window: 19
   
   2285 runs of apache/beam created since 2026-10-20T16:23:16Z (24.0 h window)
   jobs loaded: 990 runs from cache, 1295 from the API, 0 failed  (cache: 
gh-runner-usage-cache)
   
   conclusion     jobs  share runner-min runner-days
   success        4108  79.6%      72046        50.0
   cancelled       543  10.5%       5322         3.7
   skipped         261   5.1%          0         0.0
   failure         122   2.4%       4436         3.1
   in_progress     111   2.2%          0         0.0
   neutral          14   0.3%          0         0.0
   total          5159             81804        56.8
   
   average concurrent jobs over the window: 57
   
   1563 runs of apache/datafusion created since 2026-10-20T16:25:42Z (24.0 h 
window)
   jobs loaded: 1398 runs from cache, 165 from the API, 0 failed  (cache: 
gh-runner-usage-cache)
   
   conclusion     jobs  share runner-min runner-days
   success        2684  46.6%       8090         5.6
   skipped        2282  39.6%          0         0.0
   cancelled       456   7.9%       8012         5.6
   queued          271   4.7%          0         0.0
   failure          49   0.9%        185         0.1
   in_progress      10   0.2%          0         0.0
   neutral           9   0.2%          0         0.0
   total          5761             16287        11.3
   
   average concurrent jobs over the window: 11
   
   481 runs of apache/arrow-rs created since 2026-10-20T16:26:32Z (24.0 h 
window)
   jobs loaded: 310 runs from cache, 171 from the API, 0 failed  (cache: 
gh-runner-usage-cache)
   
   conclusion     jobs  share runner-min runner-days
   success        1517  71.9%       8292         5.8
   skipped         352  16.7%          0         0.0
   queued           96   4.6%          0         0.0
   failure          66   3.1%        177         0.1
   in_progress      50   2.4%          0         0.0
   cancelled        28   1.3%        466         0.3
   total          2109              8935         6.2
   ```
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to