Skip to content
GitHub Explorer

cms-dpoa/cloud-processing

View on GitHub ↗Related repositories →

Exploring the usage of public cloud resources for CMS open data processing

active 2024-05-29 → 2024-10-04 (UTC)

Partial coverage20,508 / 26,264 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-15 → 2026-08-13 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
128
Pushes
35
Pull requests
12
Issues
41
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 129 days from 2024-05-29 to 2024-10-04. Pushes: 35 total, peak 10 in a day. Pull requests: 12 total, peak 3 in a day. Issues: 41 total, peak 7 in a day. Comments: 28 total, peak 6 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
subash-taranga5420317
katilp46779
tomcordruw17822

Recent activity

Latest issues, pull requests and releases

  • Pull request#56tomcordruw2024-10-04 10:13
  • Issue#55katilp2024-10-01 20:17
    Make cmsRun output go to stdout and in a file
  • Issue#55katilp2024-10-01 19:47
    Make cmsRun output go to stdout and in a file
  • Issue#54katilp2024-09-23 05:44
    Test autopilot clusters
  • Pull request#53katilp2024-09-22 15:00
  • Issue#51katilp2024-09-22 14:34
    Use secondary boot disk for image
  • Pull request#52katilp2024-09-22 14:34
  • Pull request#52katilp2024-09-22 14:33
  • Issue#51katilp2024-09-22 13:52
    Use secondary boot disk for image
  • Issue comment#50katilp2024-09-22 08:37
    Compare E2 and C2 nodes
  • Issue#50katilp2024-09-21 21:59
    Compare E2 and C2 nodes
  • Issue comment#46tomcordruw2024-09-16 04:43
    Compare runtime/cost between high-cpu and standard cluster
  • Issue#44tomcordruw2024-09-15 16:46
    Force number of zones to 1
  • Issue comment#48tomcordruw2024-09-15 16:45
    Quantify copy time from the processing pod to NFS Vs BUCKET
  • Issue comment#48subash-taranga2024-08-31 09:59
    Quantify copy time from the processing pod to NFS Vs BUCKET
  • Issue#48subash-taranga2024-08-31 09:44
    Quantify copy time from the processing pod to NFS Vs BUCKET
  • Pull request#45tomcordruw2024-08-23 07:25
  • Issue#24tomcordruw2024-08-23 07:21
    gcs README: add the mention of the service accounts
  • Issue comment#44katilp2024-08-17 20:28
    Force number of zones to 1
  • Issue#44katilp2024-08-17 20:09
    Force number of zones to 1
  • Issue#43katilp2024-08-15 07:48
    Quantify copy time from the processing pod to nsf vs bucket
  • Issue comment#42subash-taranga2024-08-09 10:23
    Update the title: "with an NFS disk" -> "with a Google Cloud Storage (GCS) bucket"
  • Issue#42subash-taranga2024-08-09 10:23
    Update the title: "with an NFS disk" -> "with a Google Cloud Storage (GCS) bucket"
  • Issue#42subash-taranga2024-08-09 10:22
    Update the title: "with an NFS disk" -> "with a Google Cloud Storage (GCS) bucket"
  • Issue#39katilp2024-08-07 20:59
    Add a workflow that uploads the files to the disk

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.