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

Loopback transfers slower than necessary #930

Closed
cyberduck opened this issue Oct 18, 2006 · 1 comment
Closed

Loopback transfers slower than necessary #930

cyberduck opened this issue Oct 18, 2006 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

8fbae90 created the issue

I believe that transfers done on the loopback interface are running slower than is possible. I'm only getting about 120-130 KB/sec, which amounts to roughly 1 Mbit/s (right?) or 1/100th of my "theoretical" throughput on my interface... and probably quite a bit lower than that for the loopback's theoretical limit, since any loopback speed should be higher than the actual physical interfaces are rated for, shouldn't it?

(More precisely the connection is to my local machine via it's Bonjour name "Firefly.local", which I believe merely runs through the loopback instead of being broadcast and re-recieved on the wire, right?)

I am only doing this while testing out Cyberduck, so it probably has limited impact in the real world... but nonetheless, it would seem this could be quite a bit faster than it is. I mean, even if such "*.local" connections do in fact hop out of and back into the physical interface, it should still be better than 1 Mbit/s on a 100 Mbit/s interface. Might be something to optimize in the networking code somewhere... when time allows, that is.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 18, 2006

8fbae90 commented

Sorry, this may be related to #12134. It sounds like a very similar thing anyway.

I got ticket-happy today, and didn't do a search on this issue first. My apologies.

However, I'm not entirely sure that a 1% loopback speed is the same problem as a 10% local network speed. So, I'm leaving it open for your review. Thank you.

@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
Development

No branches or pull requests

2 participants