Bad speed by Upload on Win 2003

[Fireport]

I have a Problem!

On Win 2003 an IOFTPD 5.3.8r

Uploadspeed (IOFTPD): 449,61 KB/s
Uploadspeed (SERV-U): 1628,37 KB/s

Very slow uploadspeed
the downloadspeed is good!

Speedlimiting is off! I have check all parameters.

[sjabby]

i have a win2k server with the same problem
ioftpd server on upload = about 750kb/sec
bulletproof server on upload = about 8000kb/sec
serv-u serer upload = about 7500kb/sec

[Pichento]

All Windows OS's since NT4 have default TCP/IP buffers that need to be modified for large-latency transfers. Instead of explaining the full monty here, you might wanna do some reading:

Windows 2000 TCP Performance Tuning Tips (http://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm)

The magic equation being:

window size = bandwidth * delay

[Mr_X]

I made a reg files (from Windows 2000 TCP Performance Tuning Tips ).
Just add it in regedit or execute regedit /s boost.reg

[darkone]

Haven't noticed anything similar on my win2k3 (2x100mbit, no registery tweaks)

[Pichento]

D1 - it's a simple question of latency. Try uploading from long distance. w2k3 aint any different from w2k or any other OS from MS for that matter.

I've had to modify registry on all w2k3 servers so far in order to get maximum performance.

[MaistroX]

Oki, I´m thinking , as I belive most Win XP users that use ioFTPD now allso are, IS there a way to modify regestry in XP allso, to gain some extra performance to speed ? :)

[djs]

same here, win2k3 and with ioftpd i have speeds less about 20-50% (from abroad) then on glftpd. Local country speeds are almost perfect. i would appriciate any tips for tweaking this, ty for any help. :)

[Pichento]

Just read my post and modify tcpip buffers...

it applies to _all_ windows systems as i mentioned before.

[Mouton]

Let make that a poll.

[djs]

Originally posted by Pichento
Just read my post and modify tcpip buffers...

it applies to _all_ windows systems as i mentioned before.

how exactly?

i tried that boost patch, but speeds were same, even i dont have those values in registries b4. :O

[Mouton]

if u didn't have those settings, Windows was using the default (around 16kB).

You need to reboot for the new registry settings to be effective.

People: go vote on that poll I posted...

[darkone]

I just read somewhere, that one reason for bad outbound speeds could be following: receiptants receive window size is smaller that senders send window size.

[darkone]

http://www.broadbandreports.com/faq/6266 provides calculator for determinating good receive window size.

[Pichento]

darkone:

I thought you for one had read my original post :)

Its a wellknown fack that all MS OS have different send/recieve window sizes.

The very stupid idea behind this is simply that most machines will generate far more downstream than upstream AND upstream is presumably done by admins with low latency settings.

in the case of running an ftpd the opposite is the case. You always wanna kane sure upstream is at least as fast as downsteam.

The downside of modifying tcp/ip buffer i pretty simple: Memory usage will increase drasticly with high amount of sessions.

A freebsd / linux box has to my knowledge equal sized up- and downstream buffer.

All you gotta do to figure out the optimum window sizes are:

window size = bandwidth * delay

Also you _can_ add a few more tcp/ip reg values. Here is an example (all dwords in registry):

GlobalMaxTcpWindowSize
DefaultReceiveWindow
DefaultSendWindow

besides the by now usual ones:

Tcp1323Opts
TcpWindowSize

[donate]

Originally posted by darkone
I just read somewhere, that one reason for bad outbound speeds could be following: receiptants receive window size is smaller that senders send window size.

Ah so i WAS Right a few weeks ago, saying everything was "limited" @ 250kb/s, let me play around too a bit.

I should have posted it :D

-DONATE

[darkone]

Yep, however by default windows uses sliding window size. (auto adjusted by os.. not sure, if some of these 'tweaks' disable it - if it's disabled at either end, os is forced to use default window size)

[Mouton]

MSDN says those tcpwindowsize settings gives the max window size. windows starts slowly and increase if needed until this maximum is reached.
By default, those settings aren't in the registry, and are then defaulted to 16kB.
The farther you're trying to send, the larger the window should be. The bigger your internet connection, the bigger window size you'll need. Thus the formula that was pasted 12,000 times in this thread.
Your ftp server will keep throtling itself, waiting for acks from the remote server, if the window size is too small.

[Farch]

Fireport
what version of w2k3?
i have standart and I have no problems with upload

[brgr]

If uploading (maybe downloading sometimes too) is slow on a win2k3 server, then you should fix the settings of "file and printer sharing for microsoft networks" under properties of your local area connection.. or similar. Worked 4 me.