james bardin <jbar...@bu.edu> writes: > On Wed, Jun 30, 2010 at 9:33 AM, Nikolaus Rath <nikol...@rath.org> wrote: >>> Nikolaus Rath wrote: >>>> Hello, >>>> >>>> I would like to use an SFTPClient instance concurrently with several >>>> threads, but I couldn't find any information about thread safety in the >>>> API documentation. >>>> >>>> - Can I just share the SFTPClient instance between several threads? >>> > > Yes. Though you may have a use case, there's no performance benefit, > as the client can only handle one operation at a time.
I am mostly concerned about reducing the network latency. Suppose I want to create 100 1-bit files, then I hope that it is going to be faster to send 100 requests at once from 100 threads rather than having one thread that works through the files sequentially. That should still work even with a single threaded client, right? >>> Why use SFTPClient? Its performance might not be very good plus >>> compatibility issues with some SSH servers might crop up. I know I had >>> compatibility issues even with some pretty standard SSH servers on some >>> platforms (esp. Solaris). >>> > > There are throughput performance issues with older ssh servers that > don't support prefetch and pipelining. Ah, so the problem is with the server and not with the SFTPClient class? My servers are given and only speak SFTP, so I am to live with them in any case. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C _______________________________________________ paramiko mailing list paramiko@lag.net http://www.lag.net/cgi-bin/mailman/listinfo/paramiko
