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

reduce default concurrency to something more reasonable #3

Closed
soapiestwaffles opened this issue Jan 25, 2022 · 4 comments · Fixed by #22
Closed

reduce default concurrency to something more reasonable #3

soapiestwaffles opened this issue Jan 25, 2022 · 4 comments · Fixed by #22
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@soapiestwaffles
Copy link
Owner

after testing s3-nuke on a large bucket, I was able to get up to ~8000 objects/sec when I burnt out the AWS rate limit. I figure something more reasonable like 5 concurrency

@soapiestwaffles soapiestwaffles self-assigned this Jan 25, 2022
@soapiestwaffles soapiestwaffles added the enhancement New feature or request label Jan 25, 2022
@soapiestwaffles soapiestwaffles added this to the v1.1.0 milestone Jan 25, 2022
@soapiestwaffles
Copy link
Owner Author

will have to fix #5 first before I can figure out a reasonable amount of concurrency

@soapiestwaffles
Copy link
Owner Author

now that #7 is merged, going to run some tests on this

@mikelorant
Copy link
Contributor

Recommend dropping this from 100 to 5. Anything else is going to cause the rate limiter to kick in very quickly.

@soapiestwaffles
Copy link
Owner Author

agree!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants