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

[CI] Use 16 threads for interpreter tests and only run the tests on H100 #3575

Merged
merged 8 commits into from
Apr 5, 2024

Conversation

Jokeren
Copy link
Contributor

@Jokeren Jokeren commented Apr 5, 2024

No description provided.

@Jokeren Jokeren marked this pull request as ready for review April 5, 2024 01:11
@Jokeren Jokeren requested a review from ptillet as a code owner April 5, 2024 01:11
@Jokeren Jokeren requested a review from jlebar April 5, 2024 01:12
@Jokeren
Copy link
Contributor Author

Jokeren commented Apr 5, 2024

Reduced to 32s

@jlebar
Copy link
Collaborator

jlebar commented Apr 5, 2024

If 8 -> 16 threads was linear scaling (i.e. reduced the time by half), how high can we push this?

@jlebar
Copy link
Collaborator

jlebar commented Apr 5, 2024

Phil says that the H100 machine has 96 cores and the A100 machine has 24 cores.

@Jokeren
Copy link
Contributor Author

Jokeren commented Apr 5, 2024

Trying 32 now

@Jokeren Jokeren changed the title [DRAFT][CI] Use 16 threads for interpreter tests [CI] Use 16 threads for interpreter tests and only run the tests on H100 Apr 5, 2024
@Jokeren Jokeren merged commit b8049da into main Apr 5, 2024
4 checks passed
@Jokeren Jokeren deleted the keren/ci branch April 5, 2024 14:11
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