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

[DNM] Try using placement group (faster worker <-> worker network) #844

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ntabris
Copy link
Member

@ntabris ntabris commented May 10, 2023

I'm especially curious if this makes an impact on something like the vorticity test now that (in upstream dask) comms aren't slowed down by compression.

@ntabris
Copy link
Member Author

ntabris commented May 10, 2023

No improvement in transfer time on test_double_diff, but test_vorticity showed transfer time of 276.0s compared to ~285–310s on previous runs (on compressible data but with compression disabled).

So... not clear that there's improvement, but seems like there might be.

@crusaderky what do you think about doing A/B test with placement groups?

For context, placement groups let you tell Amazon you'd like your instances physically close to each other, which can improve network perf between those instances. There's a not-yet-advertised Coiled option to use a placement group for your cluster. (We don't use it by default because we've yet to see definite improvement, and it does have some impact on availability and/or time to provision cluster.)

@crusaderky
Copy link
Contributor

@crusaderky what do you think about doing A/B test with placement groups?

Sure, go on :)

@crusaderky crusaderky marked this pull request as draft July 6, 2023 17:48
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.

2 participants