"What makes you draw that conclusion? In my view this is much more likely to
be a libssh2 bug or at least flaw."

Optimism?
:)

We were linking libssh2-0.17-1.el4.rf.

We installed libssh2 0.18 (in a separate inst directory).
Despite reconfiguring libcurl to use the latest version of libssh2
(configure --with-libssh2=/home/grmdati/druFileTransfer/cesare/ssh2/) after
rebuilding libcurl and our sample code, we got similar outcomes.

Output from make and make install commands seems to confirm the correct
linking, but the new libcurl.so still points to the previous version of
libssh2.
   ldd -r CURL/lib/libcurl.so
   libidn.so.11 => /usr/lib64/libidn.so.11 (0x0000002a9569f000)
   libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x0000002a957d0000)
   ...

Our LD_LIBRARY_PATH:
echo $LD_LIBRARY_PATH
/home/grmdati/druFileTransfer/cesare/CURL/lib/:/home/grmdati/druFileTransfer
/cesare/ssh2/lib

Should we replace the system version of the package libssh2 or is there a
chance to link curl to the new installation of libssh2?

Sorry if silly questions, and thanks a lot for your support.

\c

Cesare Pietra
Value Team s.p.a.
Via del Brennero Km. 4,
Loc. La Figuretta
56123
Pisa
tel. +39 050 8009526
email: cesare.pietra_at_valueteam.com
http: www.valueteam.com

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Daniel Stenberg
Sent: venerdì 11 luglio 2008 12.58
To: libcurl development
Subject: Re: sftp performance issue

On Fri, 11 Jul 2008, cesare pietra wrote:

> Compiling curl-7.18.2-1.src.rpm on a 2 processor Linux redhat (x86_64
> GNU/Linux) box, we added support for libssh2, by configuring
-with-libssh2.
>
> Upon successful installation, we tried running a sample code snippet I'm
> catting herebye, in order to test the basic sftp get functionality.

[...]

> real 38m30.764s
> user 0m21.288s
> sys 0m7.542s

And what if you try one of the sample libssh2 applications? Do they run any
faster?

The bad performance is a known problem in libssh2, the question is just how
bad performance it "should" be.

> Isn't it weird?

That massive difference is weird indeed. Are you using the latest libssh2?

> It turns out there might be some configuration problem in the libcurl or
in
> the libssh2.

What makes you draw that conclusion? In my view this is much more likely to
be
a libssh2 bug or at least flaw.

-- 
  / daniel.haxx.se