-
Notifications
You must be signed in to change notification settings - Fork 10
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
S3 waitFor adding extra delay which changes application behavior #737
Comments
The Would adding the following comment help? await waitUntilObjectExists({
client: s3,
// Maximum wait time is required in waiters.
// Codemod uses 200 seconds as default.
maxWaitTime: 200
}, params) |
The performance issues in waiters, if any, may be caused by retry behavior of waiters. Please create a bug report on aws-sdk-js-v3 repo if you're seeing some concrete differences between v2 and v3 waiters with a minimal repro. |
Could you please observe difference with SDK V2 and V3 when no object exists? I notice it still waits for 200 seconds which was not the case before. |
The comment you mentioned would help. |
Today, I was able to see that SDK V2 exists immediately when file doesn't exist. Reproduced with "aws-sdk": "^2.1505.0".
|
Self-service
Describe the bug
SDK V2 to V3 migration using codemod is adding extra time which is causing performance issues.
transformed by codemod
The codemod adds maxWaitTime: 200 which is changing the code behavior and causing performance issues
Steps to reproduce
Try to reproduce using the provided description for command.
Observed behavior
The command waits for 200 seconds which is adding significant delay.
Expected behavior
The code would execute instantly before.
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: