Bandwith v.s Packet loss
- Thread starter sean2002
- Start date
(((===-> ** USUALLY ** <-===))) a couple packets dropped is no big deal. It's gonna depend on what the application is. Real-time video or audio will show noticable artifact with the packet drop, an FTP will not (if not excessive).
If it's a consistant value, then look at the numbers; it may be that you're gonna get X amount of bandwidth, either through dropped packets, or throttling at the MTU/Window size/etc adjustments. If you get more bandwidth, even with the packet drop, and the application doesn't see any adverse effects, then go for it.
If the packet drop adds up to more loss than the reduced-by-twiddling bandwidth, then twiddle-ho.
Some packet drop is normal (across the Internet)...it's the nature of the beast; that's why there's a re-transmit process to begin with.
Good Luck
Scott
If it's a consistant value, then look at the numbers; it may be that you're gonna get X amount of bandwidth, either through dropped packets, or throttling at the MTU/Window size/etc adjustments. If you get more bandwidth, even with the packet drop, and the application doesn't see any adverse effects, then go for it.
If the packet drop adds up to more loss than the reduced-by-twiddling bandwidth, then twiddle-ho.
Some packet drop is normal (across the Internet)...it's the nature of the beast; that's why there's a re-transmit process to begin with.
Good Luck
Scott
Scotty was hitting the nail on the head in having you look at your application quality..
Bandwidth isn't as big an issue when your talking about home usage since your not trying to make money off of your throughput (your not right *wink* *wink*)
Check your games, video feed, download, upload, and all the internet type applications and if they are within usability then do nothing. Or you could try the tweak out for a while and see how that goes and whether your experience is better.
Its all about how you percieve the experience since bandwidth means nothing unless you are using it for something.
Bandwidth isn't as big an issue when your talking about home usage since your not trying to make money off of your throughput (your not right *wink* *wink*)
Check your games, video feed, download, upload, and all the internet type applications and if they are within usability then do nothing. Or you could try the tweak out for a while and see how that goes and whether your experience is better.
Its all about how you percieve the experience since bandwidth means nothing unless you are using it for something.
If you were getting consistant packet loss, say 50%, what could some of the problems be?
A few times while having troubles with my DSL connection, my pings to a 4-5 hop distance away were getting close to 75% packet loss.
Would that indicate a problem with the network or devices beyond the Telco lines?
TIA
A few times while having troubles with my DSL connection, my pings to a 4-5 hop distance away were getting close to 75% packet loss.
Would that indicate a problem with the network or devices beyond the Telco lines?
TIA
It's usually high latency (like from congestion).
Part of "The Great Lie of DSL" is "everyone gets a dedicated connection:" they do, but only for the local loop. Once all the LLs aggregate back to some POP, they're stuffed into a (usually) well oversubscribed fat pipe (DS3/OC3, maybe an OC12). Covad has a pretty bad reputation for doing this...it was so bad around Chicago, SpeakEasy.net built their own POP so they could get their customer's throughput back up to an acceptable level.
Crappy lines will cause a lot of re-transmissions too. When you get up into the 50% range, it almost sounds more like a hardware misconfiguration (like a duplex mismatch, or really bad termination / out-of-spec cable).....usually on the user's part of the network.
If you get that kind of Pdrop, and it's "fer sher" on the provider's side, then it's hole & pole time for those guys...something that requires a sh*tload of time on the support line going through "The Procedures" until they're exhausted...then MAYBE they'll check their line...then Maybe they'll decide their network/infrastructure has a problem....
FWIW
Scott
Part of "The Great Lie of DSL" is "everyone gets a dedicated connection:" they do, but only for the local loop. Once all the LLs aggregate back to some POP, they're stuffed into a (usually) well oversubscribed fat pipe (DS3/OC3, maybe an OC12). Covad has a pretty bad reputation for doing this...it was so bad around Chicago, SpeakEasy.net built their own POP so they could get their customer's throughput back up to an acceptable level.
Crappy lines will cause a lot of re-transmissions too. When you get up into the 50% range, it almost sounds more like a hardware misconfiguration (like a duplex mismatch, or really bad termination / out-of-spec cable).....usually on the user's part of the network.
If you get that kind of Pdrop, and it's "fer sher" on the provider's side, then it's hole & pole time for those guys...something that requires a sh*tload of time on the support line going through "The Procedures" until they're exhausted...then MAYBE they'll check their line...then Maybe they'll decide their network/infrastructure has a problem....
FWIW
Scott
<< Once all the LLs aggregate back to some POP, they're stuffed into a (usually) well oversubscribed fat pipe >>
AND THAT IS WHY PROVIDERS SHOULD CHARGE EXTRA FOR EXTRA COMPUTERS.
The side that causes trouble and heated debate.
I gotta red hot poker here and I just gotta use it.
I gotta red hot poker here and I just gotta use it.
the question makes no sense....
if the packets are dropped, they have to be re-sent, thats how TCP/IP works. So if you have packetloss, you're wasting bandwith, because the info has to be transfered again.
Anything over 2% packetloss means someone isn't doing thier job. (not that its not common)
bart
if the packets are dropped, they have to be re-sent, thats how TCP/IP works. So if you have packetloss, you're wasting bandwith, because the info has to be transfered again.
Anything over 2% packetloss means someone isn't doing thier job. (not that its not common)
bart
<< the question makes no sense....
if the packets are dropped, they have to be re-sent, thats how TCP/IP works. So if you have packetloss, you're wasting bandwith, because the info has to be transfered again.
Anything over 2% packetloss means someone isn't doing thier job. (not that its not common)
bart[/q
Well, don't forget UDP. They operate in a "Hey, I'm sending this, I won't ask for a response but I hope you get it!" type of thing. That's different from TCP itself.
I am, of course, assuming you are using the term TCP/IP as in the whole suite. Which you probably aren't doing!
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter