Bad speed by Upload on Win 2003

Fireport · 11-23-2003, 04:37 PM

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 · 11-23-2003, 04:46 PM

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 · 11-23-2003, 05:46 PM

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

The magic equation being:

window size = bandwidth * delay

Mr_X · 11-23-2003, 06:51 PM

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

darkone · 11-24-2003, 01:23 AM

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

Pichento · 11-24-2003, 04:37 AM

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 · 11-24-2003, 05:19 AM

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 · 11-24-2003, 05:52 AM

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 · 11-24-2003, 07:05 AM

Just read my post and modify tcpip buffers...

it applies to _all_ windows systems as i mentioned before.

Mouton · 11-24-2003, 11:44 AM

Let make that a poll.

djs · 11-24-2003, 04:52 PM

Quote:

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 · 11-24-2003, 07:48 PM

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 · 11-25-2003, 05:02 AM

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 · 11-25-2003, 06:24 AM

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

Pichento · 11-25-2003, 06:41 AM

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