On Sat, 11 Aug 2018, Daniel Jeliński wrote:
I like that; if we had the sftp_write function acknowledge data as soon as
it is put in socket buffer, we could get much faster transfers. In order to
avoid errors we would need to wait for all outstanding acks on file close.
Something like that,
pt., 10 sie 2018 o 23:08 Daniel Stenberg napisał(a):
> [...] libssh2 could offer a better API that's more suited to send (and
> receive) SFTP data.
I like that; if we had the sftp_write function acknowledge data as
soon as it is put in socket buffer, we could get much faster
transfers. In
On Fri, 10 Aug 2018, Daniel Jeliński via curl-library wrote:
TCP window is not a problem, and SSH window doesn't seem to be the
problem either. There is definitely still some room for improvement.
Absolutely. For example, one fundamental piece that is a rather tough obstacle
is the fact that
Ok, so let's put Linux to a test.
0. Patch CURL:
#define UPLOAD_BUFSIZE (1<<19)
1. Create a large file. 1 TB looks good:
dd if=/dev/zero of=testfile bs=1 count=0 seek=1T
The file is sparse, so disk operations won't block us.
2. Upload to /dev/null:
curl -u user:pass -k sftp://127.0.0.1/dev/null -T
Jan Ehrhardt via curl-library (Fri, 10 Aug 2018 17:25:51 +0200):
>running curl-mingw64 sftp
> % Total% Received % Xferd Average Speed TimeTime Time Current
> Dload Upload Total SpentLeft Speed
>100 274M0 0 100 274M 0 298k
Jan Ehrhardt via curl-library (Fri, 10 Aug 2018 03:29:21 +0200):
>Gisle Vanem via curl-library (Thu, 9 Aug 2018 18:31:12 +0200):
>>Jan Ehrhardt wrote:
>>
Wow dude! 2 times faster than FileZilla now.
Time decreased from 33.153s to 6.4 sec (same random 10 MByte file).
Versus
On Tue, 7 Aug 2018, cjmsoregan via curl-library wrote:
I have run into an issue in libcurl where the uploaded size obtained via
CURLINFO_SIZE_UPLOAD is not measured correctly if the Expect header is
removed.
Thank you!
I could reproduce the issue using your code. I first submitted it as a
