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

Performance issue clearing transfer window with many items #12482

Closed
cyberduck opened this issue Jul 7, 2006 · 1 comment
Closed

Performance issue clearing transfer window with many items #12482

cyberduck opened this issue Jul 7, 2006 · 1 comment
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 7, 2006

jerdonek created the issue

(Old summary: warn users to 'clear' transfer window or else significantly speed transfer window loading)

When the transfer window has several hundred items, Cyberduck hangs and slows the entire computer when loading the transfer window. This lasts more than a minute (up to 5 minutes or more for some).

This can be solved by pressing "Clear" in the transfer window, but there is no way for a user to know that this is the solution to the slowdown.

Incidentally, 'clearing' the transfer window can also take forever if there are several hundred items. I waited 30 minutes before force-quitting Cyberduck. It seems that manually selecting and scrolling items and 'removing' them causes no such delay.

My suggestion is to either considerably speed the loading of the transfer window so there is no visible delay, or else somehow warn the user to clear the transfer window when the window gets to a certain size (e.g. 50 items). But I don't see why it should take a long time to load the window. It's merely a list of things, right?

Note: I haven't confirmed this behavior on newer versions of Cyberduck (using Version 2.4b2).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 7, 2006

jerdonek commented

Another option is to give the transfer window a maximum size. The oldest items will start getting deleted when the maximum size is reached. The maximum can be set in the Cyberduck preferences. The default can be set at 40. 'No maximum' can also be an option for 'power users.' :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants