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.

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

roachtest: use n1-standard for 16-core GCE machines #88346

Merged
merged 1 commit into from
Sep 22, 2022

Conversation

erikgrinaker
Copy link
Contributor

@erikgrinaker erikgrinaker commented Sep 21, 2022

Roachtest used n1-highcpu machines at 16 cores and beyond. However, this causes a memory cliff, because a n1-standard-8 machine has ~30 GB memory (3.75 GB per core), but a n1-highcpu-16 machine only has 14 GB memory (0.9 GB per core).

This patch makes 16-core machines use n1-standard as well, with 60 GB memory, and only switches to n1-highcpu at 32 cores (with 29 GB memory).

Touches #87809.

Release note: None

@erikgrinaker erikgrinaker requested a review from a team as a code owner September 21, 2022 14:03
@erikgrinaker erikgrinaker self-assigned this Sep 21, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@srosenberg
Copy link
Member

This patch makes 16-core machines use n1-standard as well, with 60 GB memory, and only switches to n1-highmem at 32 cores (with 29 GB memory).

Typo, should be n1-highcpu-32?

Roachtest used `n1-highcpu` machines at 16 cores and beyond. However,
this causes a memory cliff, because a `n1-standard-8` machine has ~30 GB
memory (3.75 GB per core), but a `n1-highcpu-16` machine only has 14 GB
memory (0.9 GB per core).

This patch makes 16-core machines use `n1-standard` as well, with 60 GB
memory, and only switches to `n1-highcpu` at 32 cores (with 29 GB
memory).

Release note: None
@erikgrinaker
Copy link
Contributor Author

Typo, should be n1-highcpu-32?

Yep, thanks!

bors r=srosenberg

@craig
Copy link
Contributor

craig bot commented Sep 22, 2022

Build succeeded:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants