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

Mitigate Azure object store stragglers by limiting gateway connections #594

Merged
merged 6 commits into from
Oct 6, 2022

Conversation

parasj
Copy link
Contributor

@parasj parasj commented Oct 4, 2022

Past 24 connections, Azure blob or Azure auth begins to throttle performance. This PR sets a default limit of 24 connections for Azure.

Copy link
Member

@ShishirPatil ShishirPatil left a comment

Choose a reason for hiding this comment

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

Chunking is an artifact introduced by skyplane, and chunk # is not an underlying object (thought here is a 1-1 mapping). This information is critical for debugging, but is not relevant to the user. If I know there are 3 chunks remaining that might be Ok, though I don't see how that would be useful beyond informatics. The additional chunk id in-itself maybe is not so useful.

Is there any reason why you thought it would be good to print this out?

@parasj parasj enabled auto-merge (squash) October 6, 2022 17:12
@parasj
Copy link
Contributor Author

parasj commented Oct 6, 2022

@ShishirPatil These stats were useful for debugging stragglers, but I agree it shouldn't be user facing. I gated off that logic with a debug flag.

@parasj parasj merged commit 558ccb7 into main Oct 6, 2022
@parasj parasj deleted the dev/azure_straggler branch October 6, 2022 17:19
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