Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Batch C-Test: 32 vCPU Compute Environment with 1 vCPU per job #1017

Open
wants to merge 3 commits into
base: avrohom/b-test-16-vcpus-half-vcpu-per-job
Choose a base branch
from
Open

Batch C-Test: 32 vCPU Compute Environment with 1 vCPU per job #1017

wants to merge 3 commits into from

Conversation

avrohomgottlieb
Copy link
Contributor

@avrohomgottlieb avrohomgottlieb commented Dec 6, 2024 •
edited
Loading

Issue Number

N/A

Purpose/Implementation Notes

For the Batch C-test, the following changes were made:

  • Updated job_definition to increase vcpus per job to 1.0 (after B-Test reduced it to 0.5 per job)
  • Updated compute_environment to a 32 vcpu pool
  • Updated batch_tags to reflect this change

Types of changes

What types of changes does your code introduce?

  • New feature (non-breaking change which adds functionality)

Functional tests

N/A

Checklist

N/A

Screenshots

N/A

@avrohomgottlieb avrohomgottlieb changed the title Go up to 32 vCPUs on Batch For B-Test Batch C-Test: 32 vCPU Compute Environment with 1 vCPU per job Dec 9, 2024
@avrohomgottlieb avrohomgottlieb changed the base branch from dev to avrohom/b-test-16-vcpus-half-vcpu-per-job December 9, 2024 18:18
davidsmejia
davidsmejia approved these changes Dec 9, 2024
View reviewed changes
Copy link
Contributor

@davidsmejia davidsmejia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might need to merge in dev for this to take

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@davidsmejia davidsmejia davidsmejia approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@avrohomgottlieb @davidsmejia