Re: Why is secure FTP via SSH2 going so sloooooow?
From: Will Ashford (ashford_at_virginia.edu)
Date: 04/19/05
- Next message: Mark: "Re: secure file delete on journaled file systems"
- Previous message: Dragan Cvetkovic: "Re: Root passwd change not working"
- In reply to: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Next in thread: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Reply: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 18 Apr 2005 22:06:00 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wim Cossement wrote:
>> Have you checked to be sure that the problems aren't at the other end of
>> the SSH connections? The same memory and CPU usage caveats apply there,
>> and if those boxes don't respond quickly then your server will
>> probably be
>> idling while it is waiting for them.
>
>
> Well I tried with a P4 2.7 laptop, 512 MB RAM running WinXp, and there
> the CPU and RAM usage are fine.
>
>> Are you running identical software on all your clients, and if not, are
>> there performance differences among them?
>
>
> OpenSSH on the servers, FileZilla on the Windows Clients.
> We also have a few Linux boxes, (dual 2.2 Xeons and 2 Gigs of RAM), and
> if I connect to those ones from my Win PC (1.7 Athlon XP, 512 MB RAM) I
> get about 200 K a connection.
>
>> When you say "about 70 Kbps", what happens to your server output speed
>> when say two clients are connected (and actively transferring data)?
>> ie.:
>> Does your server output go to 140 Kbps, or does each client drop to 35
>> Kbps?
>
>
> Well, FileZilla uses 4 threads (fedault perhaps?), so each of them gets
> 60-70 Kbps
>
>> .... If the former, then whatever issues exist are on the client end.
>> .... If the latter, then the issues are on the server.
>
>
>
> I'll try connection from one Linux box to another with KBear or so (if
> this can use SSH2 for FTP)
>
> Wimmy
I know that until a short while ago, there was a known bug with PuTTY's
sftp client (an implementation of which FileZilla uses) that caused
transfers going over SSH2 to be drastically slow. They may have fixed it
in the latest PuTTY build. To see if this is the problem, try using
WinSCP ( winscp.net ) to transfer the files on the windows client side.
Will
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCZGeIkIdrTCWKJM0RAuZRAJ94xnl66iICYkpa7dunjmyYiHdL8QCdHWGD
QkVuMNAeN9tzbZw1nt9GlSI=
=BkC2
-----END PGP SIGNATURE-----
- Next message: Mark: "Re: secure file delete on journaled file systems"
- Previous message: Dragan Cvetkovic: "Re: Root passwd change not working"
- In reply to: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Next in thread: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Reply: Wim Cossement: "Re: Why is secure FTP via SSH2 going so sloooooow?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|