On Thu, 7 Feb 2013, Christian Hägele wrote:
Optimizing for very high bandwidth (over 100MBit/s) might need some
additional work on the internals of curl which are out of scope of the issue
you described.
I agree. But we could start with documenting the results and suggestions
somwhere, of
Hello
I finally received access to slow upload machine config. First of all: the ping
value is 57ms (it's even worse than i thought), netsh interface tcp global
values are the same as described in previous messages.
I made several curl builds: with modified CURL_MAX_WRITE_SIZE (MAX) and
On Wed, 6 Feb 2013, Kurushin Andrey wrote:
1. the main bug report (filezilla vs far manager vs curl) contains test of
cross-countries test results (ping 8ms). recent tests (with custom builds
of 7.28.1) were made inside single subnet (ping 1ms) so they have better
speed values.
Well, 8 vs
Kurushin Andrey ajax16384 at gmail.com writes:
1. the main bug report (filezilla vs far manager vs curl) contains test of
cross-countries
test results (ping 8ms). recent tests (with custom builds of 7.28.1) were
made inside single subnet (ping
1ms) so they have better speed values.
1. the main bug report (filezilla vs far manager vs curl) contains test of
cross-countries
test results (ping 8ms). recent tests (with custom builds of 7.28.1) were
made inside single subnet (ping 1ms) so they have better speed values.
2. CURL_MAX_WRITE_SIZE = 16kb and SO_SNDBUF=8mb gives
On Tue, 5 Feb 2013, Pierre Joye wrote:
But yes, it needs improvements here. I can't think of any better way to
solve this than to detect OS level at run-time and only SNDBUF if =
windows 2008, so that Vista and later won't get it changed.
It is possible to detect at runtime the OS version
hi!
On Tue, Feb 5, 2013 at 11:05 AM, Daniel Stenberg dan...@haxx.se wrote:
On Tue, 5 Feb 2013, Pierre Joye wrote:
But yes, it needs improvements here. I can't think of any better way to
solve this than to detect OS level at run-time and only SNDBUF if = windows
2008, so that Vista and later
Hello
According to my investigation at http://sourceforge.net/p/curl/bugs/1188/#ca3a
skipping of SO_SNDBUF adjustment does not solve low performance.
Thanks
Andrei
05.02.2013, в 19:50, Pierre Joye pierre@gmail.com написал(а):
hi!
On Tue, Feb 5, 2013 at 11:05 AM, Daniel Stenberg
Курушин Андрей ajax16384 at gmail.com writes:
According to my investigation at http://sourceforge.net/p/curl/bugs/1188/#ca3a
skipping of SO_SNDBUF adjustment does not solve low performance.
I looked at your patch and that solved my issue with slow performance. I
did not try to change the
win2k8r2 settings during previous tests:
TCP Global Parameters
--
Receive-Side Scaling State : enabled
Chimney Offload State : automatic
NetDMA State: enabled
Direct Cache Acess (DCA):
Thank you for your input. That rules out some misconfiguration in windows.
In my opinion CURL_MAX_WRITE_SIZE should not have a big effect on the speed,
because the TCP-stack shouldn't care in what chunks the application wants to
send
data over the TCP-connection. It can have an effect if the
On Tue, 5 Feb 2013, Christian Hägele wrote:
So i have 2 questions as follow up:
Just a quick addition from me as well: stick with comparing plain (unencrypted
FTP) to begin with so that we know it is plain and simple socket usage we play
with.
SFTP is an *entirely* different beast and for
On Fri, 1 Feb 2013, Christian Hägele wrote:
The problem described in http://support.microsoft.com/kb/823764 doesn't
seems to apply to Win-Vista. So do you mean Curl_sendbufset() should not be
set for Vista/2008 R2? If so, there should be an adaption to the running
Windows version. Try it;
On Mon, 4 Feb 2013, Christian Hägele wrote:
You are right that this is ugly if you were dependent on that workaround.
However, I believe that not many people are experience these problems. I
don't know when the CURL_MAX_WRITE_SIZE was lowered from 20Kib to 16KiB, but
there is a chance that
Christian Hägele haeg...@teamviewer.com wrote:
The reason for that is the Curl_sndbufset-function in connect.c. On windows the socket-sendbuffer is set to a value of
CURL_MAX_WRITE_SIZE + 32 (16416 bytes). There is a also a strange comment why this is done.
When the SO_SNDBUF is not
Am 01.02.2013, 13:47 Uhr, schrieb Gisle Vanem gva...@broadpark.no:
Did you also see the comment in include/curl/curl.h?
'CURL_MAX_WRITE_SIZE'
can be set a compile-time. I suggest you do that to not make transfer
slower
for people using an older Windows (Win-XP).
The size of 16KiB
16 matches
Mail list logo
