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
This PR enables building on a custom runner hosted on EC2 using p2.xlarge instances for PREVIEW builds
These instances have:
1 x NVIDIA K80 GPU
4 x vCPU's
All setup and use of EC2 is automated and works the same way as the previous Preview Workflow Script.
The cml runner manages the EC2 instance so the instance only runs when preview builds are running. As a result it takes a little longer to setup as it fetches a fresh instance each time a preview build runs. It then uses a Docker image based on ubuntu and installs anaconda etc. However this means we are only paying for EC2 when previews are getting built and the instance is torn down when the preview run is completed. This makes this option very cost effective.
@jstac I propose I enable the following custom build runner workflow (which builds on EC2) for previews only and do some test run on the next few PR's, before we look at publishing from these runs.
So GPU support is available currently for:
previews
publishing
The publishing will need to be enabled in a subsequent PR.
Note: Test build cache workflows to ensure that works the same way as GitHub Actions hosted workflow.
@HumphreyYang I will merge this PR soon which will change how previews are build via GitHub Actions. It would be great if you could take close looks at previews for the next couple of changes and let me know if you can spot any issues.
This PR is bringing the ability to build code that requires access to a GPU so we can test this out on #237
@HumphreyYang I will merge this PR soon which will change how previews are build via GitHub Actions. It would be great if you could take close looks at previews for the next couple of changes and let me know if you can spot any issues.
This PR is bringing the ability to build code that requires access to a GPU so we can test this out on #237
Thanks @mmcky. I will keep an eye on the new previews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mmcky
changed the title
This PR enables building on a custom runner hosted on EC2 using
p2.xlargeinstances for PREVIEW buildsThese instances have:
All setup and use of EC2 is automated and works the same way as the previous Preview Workflow Script.
The
cmlrunner manages the EC2 instance so the instance only runs when preview builds are running. As a result it takes a little longer to setup as it fetches a fresh instance each time a preview build runs. It then uses a Docker image based onubuntuand installs anaconda etc. However this means we are only paying for EC2 when previews are getting built and the instance is torn down when the preview run is completed. This makes this option very cost effective.Checks
QuantEcon/meta#56