You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GPU runners: track alternatives to the RunsOn custom AMI #183
GPU lecture builds (lecture-python.myst) run on RunsOn with a custom AMI, which needs AMI maintenance and Packer rebuilds (docs/dev/GPU-AMI-SETUP.md). Two alternatives were recorded in docs/FUTURE-DEVELOPMENT.md, which #178 removed (source). This issue keeps them tracked.
Alternatives
GitHub-hosted GPU runners
No AMI to maintain; the runner is selected with runs-on:.
Availability and pricing need checking before this is worth evaluating.
Trade-off: likely more expensive per minute than RunsOn, and possibly less choice of instance and GPU type.
A GPU container on an nvidia/cuda base
CUDA and cuDNN pre-installed next to the scientific Python stack.
Matches the container pattern the CPU builds already use.
Still needs a GPU runner (RunsOn or GitHub-hosted) started with --gpus all.
Trade-off: an image of roughly 15–20 GB, so pull time could cancel out the setup savings unless layer caching works well.
Activity
docs(plan): record #194's outcome: link checks stay per repository, #185