LoBo

[SVO-1]

hey man - this aint bad i guess but you got any ideas to make it better
- - -
athalon 600 / 205 ram <50 ramdrive> / w98se / ie6
- - -
Test Results:
Test file size: 500 KB
Download time: 3.95 seconds
Estimated line speed: 1012.7 Kbps
Estimated transfer rate: 126.6 KB/sec.
- - -
TCP options string = 020405b40103030301010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which is equal to MSS.
Default Receive Window (RWIN) = 321200
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 40150
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 12848 kbps (1606 KBytes/s) @ 200ms
Your RcvWindow limits you to: 5139.2 kbps (642.4 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
- - -
i just had to reinstall windows but i set everything back up like it was - use to be faster though b4 crash.

[HalfLifer]

No need for system specs, all you need is OS and paste your results.

[SVO-1]

why - it makes a difference doesn't it ?

[SVO-1]

bump - :)

[Lobo]

Becauuse CPU size does matter I would try as RWIN 64240, 513920, 522680 or 524176:) :)

[HalfLifer]

Originally posted by Lobo
Becauuse CPU size does matter I would try as RWIN 64240, 513920, 522680 or 524176:) :)


No, it does not. For the record, Rwin is the # of bytes you are willing to receive before sending an Ack (a TCP Acknowledgment ). The downfall of having a large Rwin is packet retransmission.
If you set your Rwin to 100 (as an example), once you recieve 100 bytes of data from the sender the sender stops sending any more packets until the receiver sends an Ack that all the packets made it correctly. If the one of the packets was lost or corrupted on route to the receiver, an Ack will not be sent. This means the sender waits for a while for the Ack (TCP timeout) and will eventually retransmit all the packets it just sent - which in this case would be 100 bytes.
Now consider an Rwin set to 200000. If a single packet becomes lost or corrupt, the sender must resend all 200000 bytes (even if on 1 packet didn't make there).
The point is, if you don't have much packet loss (which you hopefully don't) then a large Rwin can greatly improve dl performance of TCP applications (such as ftp). If you do experience some packetloss however, your speeds will actually see a dramatic decrease.

[Lobo]

Media Access Control (MAC)
The MAC sits between the upstream and downstream portions of the cable modem, and acts as the interface between the hardware and software portions of the various network protocols. All computer network devices have MACs, but in the case of a cable modem the tasks are more complex than those of a normal network interface card. For this reason, in most cases, some of the MAC functions will be assigned to a central processing unit (CPU) -- either the CPU in the cable modem, or the CPU of the user's system. Hence, the CPU does affect the speed of the cable modem as does the NIC. All NIC's use some CPU cycles to process information. If the CPU is faster, then the processing of that info will be faster and therefore download and uploads will be faster...this can be found on the site http://www.howstuffworks.com/

:) :)

[HalfLifer]

Originally posted by Lobo
Media Access Control (MAC)
The MAC sits between the upstream and downstream portions of the cable modem, and acts as the interface between the hardware and software portions of the various network protocols. All computer network devices have MACs, but in the case of a cable modem the tasks are more complex than those of a normal network interface card. For this reason, in most cases, some of the MAC functions will be assigned to a central processing unit (CPU) -- either the CPU in the cable modem, or the CPU of the user's system. Hence, the CPU does affect the speed of the cable modem as does the NIC. All NIC's use some CPU cycles to process information. If the CPU is faster, then the processing of that info will be faster and therefore download and uploads will be faster...this can be found on the site http://www.howstuffworks.com/

:) :)


Wrong again Lobo. RWIN, etc deal with TCPIP not cpu power.

[Lobo]

Let the man decide with one works best for him, it does not matter to me, as long as he is satisfied:)