TortoisePlink performance

Hello,

The TortoiseHg project has been using your TortoisePlink application
as our default ssh transport for a couple of years. A while ago some
performance problems [1] were raised with it and just recently I had
the opportunity to investigate in more detail. I compared a clone[2]
operation using several tools and configurations, and this is what I
found (apologies for ascii table art):

openssh -C: 0:30
openssh: 1:10
Plink: 1:20
paramiko: 2:00
TortoisePlink: 4:00

I built Plink and TortoisePlink myself to get the tip version of each.
 The clone time for both Plink and TortoisePlink was unchanged when
using the -C compression option. I suspect the compression was only
being used for upstream direction, but that's speculation on my part.

The executive summary is there seems to be a lot to gain from pulling
the tip of Plink into TortoisePlink.

--
Steve Borho
[1] http://bitbucket.org/tortoisehg/stable/issue/139/very-poor-performance-using-tortoiseplinkexe-even-with
[2] clone is a mercurial command for replicating a repository
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2478678
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].