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

Long transcript slows down operation #6036

Closed
cyberduck opened this issue Jun 25, 2011 · 4 comments
Closed

Long transcript slows down operation #6036

cyberduck opened this issue Jun 25, 2011 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 25, 2011

Tim Coop3R created the issue

I have noticed some interesting behaviour when deleting a very large number of files from S3 using Cyberduck.

When removing a bucket containing around 14,000 files a request is sent to delete each file one at a time (as best as I can tell). If you leave this operation to run and return after 20 or 30 minute you will notice that in the Log draw the operation is now happening much more slowly to the point that the log messages are easily readable as they pass through the windows1 or two a second.

If you stop the operation, disconnect, re-connect and start the operation again the operation resumes at full speed with the operations passing the log window faster than you can read them at the rate of several every second.

This is repeatable and has happened the last 3 or 4 times I have run this operation.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2011

@dkocher commented

The performance impact is most possibly due to the large amount of lines in the transcript and automatically scrolling to the last appended line in the log drawer. Closing the log drawer (⌘-L) should resolve this.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2011

Tim Coop3R commented

So it does! Thanks

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 26, 2011

@dkocher commented

We should possibly clear the transcript at a certain limit if the performance impact is too big.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 27, 2012

@ylangisc commented

In c34dfaa.

Loading

@cyberduck cyberduck closed this Dec 27, 2012
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants