poor cable d/l speed
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
poor cable d/l speed
where do i begin? i have been on cable for about two weeks. lost over half the speed i had with dsl(moved). called and complained about d/l speed, got the run around about gaurenteed minimums. requested half price, which was granted due to lack of mentioning from sales rep. when i test d/l at dslreports it says i get a d/l speed of 1470. when i d/l at all the other places it says i d/l at the average of 345 Kbps. transfer rate on d/l's is average of 43KB/sec. i am very frustrated after having much better speeds with dsl. like i said my speed dropped over half. i'm stuck with cable cuz dsl doesn't come here to where i moved. i am throwing up one last ball of hope that i can be helped here.
Receive Window (RWIN): 256960
Window Scaling: 2
Path MTU Discovery: ON
RFC1323 Window Scaling: ON
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL: unknown
TTL remaining: 52
Notes and recommendations:
Choose RWIN between 14600 and 37960 (FAQ #586)
download/use DRTCP .. (FAQ #578)
Read the tweak FAQ
Example 146000 byte download
Actual data bytes sent: 167900
Actual data packets: 115
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 15
sacks you sent: 36
pushed data pkts: 2
data transmit time: 0.605 secs
our max idletime: 137.1 ms
transfer rate: 153649 bytes/sec
transfer rate: 1229 kbits/sec
This is not a speed test!
transfer efficiency: 86%
TCP options string = 020405b40103030201010402
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) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
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)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 51 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
hope this isn't too much info at once, thanks in advance
seeker_of_knowledge
Receive Window (RWIN): 256960
Window Scaling: 2
Path MTU Discovery: ON
RFC1323 Window Scaling: ON
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL: unknown
TTL remaining: 52
Notes and recommendations:
Choose RWIN between 14600 and 37960 (FAQ #586)
download/use DRTCP .. (FAQ #578)
Read the tweak FAQ
Example 146000 byte download
Actual data bytes sent: 167900
Actual data packets: 115
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 15
sacks you sent: 36
pushed data pkts: 2
data transmit time: 0.605 secs
our max idletime: 137.1 ms
transfer rate: 153649 bytes/sec
transfer rate: 1229 kbits/sec
This is not a speed test!
transfer efficiency: 86%
TCP options string = 020405b40103030201010402
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) = 256960
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 64240
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)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 51 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
hope this isn't too much info at once, thanks in advance
seeker_of_knowledge
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
OK, and did they improve your connection at all?Originally posted by seeker_of_knowl
these are the patched settings
Where are you testing your connection? Make sure your not mixing up bit and bytes. Most speed testing sites measure in bits while web browsers show transfers as bytes.
JFYI, you will not be able to exceed any caps.
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
- Cable_Dood
- Regular Member
- Posts: 210
- Joined: Fri Jan 25, 2002 3:53 pm
- Location: In the Monolith
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
this is the test after going back to win98,
thanks for your responses
TCP options string = 020405b401010402
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) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535
Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to 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: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 115 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
thanks for your responses
TCP options string = 020405b401010402
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) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535
Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to 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: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 115 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00000000
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
bro, i reformatted and left out the tweaks and win2k is now allowing me to transfer at the 1.9mbps barrier. it wasn't the win2k issue with my nic after all, it was the fact that i couldn't fully remove the tweaks from my registry. i have been advised not to add the tweaks to my system, being that is what was causing the poor d/l speed. i can't explain it, with the tweaks i only was able to transfer a d/l at 44KB per sec.... i reformatted and left the tweaks off and now have a d/l transfer rate of 233kb per sec.
and yes, i did run the auto restore to default settings. even tried manualy changing them to and deleting the tweaks.
can't figure it out but i'm not interested in figuring it out, i got what i wanted by removing the tweaks.
i can understand if anyone feels they need to defend the tweaks, but i wish not to engage in any conflicts, i found the solution to my problem.
thanks for all you guys's help
and yes, i did run the auto restore to default settings. even tried manualy changing them to and deleting the tweaks.
can't figure it out but i'm not interested in figuring it out, i got what i wanted by removing the tweaks.
i can understand if anyone feels they need to defend the tweaks, but i wish not to engage in any conflicts, i found the solution to my problem.
thanks for all you guys's help
-
seeker_of_knowl
- Member
- Posts: 21
- Joined: Mon Mar 18, 2002 11:53 am
- Location: north of Pittsburgh
Yeah, the tweaks don't work for everyone, but do for the majority. I'm not using any right now, but I'm also hitting my cap (768 SDSL). Back when I had cable and residential DSL, I didn't use them either and was always able to hit my cap (in case of the DSL) or the tweaks made no difference (in case of the cable).